tea pr: showing CI status of merged PR always fails #318
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#318
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
..because
pr.Head.Sha
is empty on a PR with deleted head branch.Not sure if we can do something about this. It's weird, because the web UI still has the history, and the CI result is still stored under the original commit.
If we can't fix it, we should handle it better than printing
error while loading CI: 404 Not Found
This should be a bug of Gitea.
upstream issue https://github.com/go-gitea/gitea/issues/12675
hmm shold I add the workaround into the sdk?
ref: https://github.com/go-gitea/gitea/issues/12675#issuecomment-685903482
@6543 I don't understand that workaround, how do you query for a commit without the SHA?
Otherwise a workaround would be nice, so things work with older gitea versions
I also noticed that we depend on this gitea bug here (I thought it was intended behaviour ;):