Fix merge dialog on protected branch with missing required statuses #11074
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GiteaBot
added
the
lgtm/need 2
6543
changed the title
Codecov Report
@@ Coverage Diff @@
## master #11074 +/- ##
==========================================
+ Coverage 43.50% 43.52% +0.01%
==========================================
Files 598 598
Lines 84771 84769 -2
==========================================
+ Hits 36877 36893 +16
+ Misses 43353 43335 -18
Partials 4541 4541
Continue to review full report at Codecov.
|
lafriks
approved these changes
Apr 15, 2020
GiteaBot
added
lgtm/need 1
guillep2k
approved these changes
Apr 15, 2020
GiteaBot
added
lgtm/done
zeripath
approved these changes
Apr 15, 2020
6543
changed the title
zeripath
changed the title
Contributor
|
Make lg-tm work |
6543
added a commit
to 6543-forks/gitea
that referenced
this pull request
Apr 15, 2020
…o-gitea#11074) It is possible for misconfigured protected branches to have required status checks that are not in any of the current statuses: Pending, Success, Error, Failure, or Warning - presumably because the CI has not contacted us as yet. Fix go-gitea#10636 by adding case: missing StatusChecks when these are missing
Member
Author
|
Backport send #11084 |
lafriks
pushed a commit
that referenced
this pull request
Apr 16, 2020
…11074) (#11084) It is possible for misconfigured protected branches to have required status checks that are not in any of the current statuses: Pending, Success, Error, Failure, or Warning - presumably because the CI has not contacted us as yet. Fix #10636 by adding case: missing StatusChecks when these are missing
ydelafollye
pushed a commit
to ydelafollye/gitea
that referenced
this pull request
Jul 31, 2020
…o-gitea#11074) It is possible for misconfigured protected branches to have required status checks that are not in any of the current statuses: Pending, Success, Error, Failure, or Warning - presumably because the CI has not contacted us as yet. Fix go-gitea#10636 by adding case: missing StatusChecks when these are missing
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is possible for misconfigured protected branches to have required status checks that are not in any of the current statuses: Pending, Success, Error, Failure, or Warning - presumably because the CI has not contacted us as yet.
Fix #10636 by adding case: missing StatusChecks when these are missing