Restore warning commit status (#27504) #27529
Merged
Conversation
This file contains 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
Partial revert of go-gitea#25839. This commit status is used by a number of external integrations, so I think we should not remove it (See go-gitea#25839 (comment)). This is a rare case where an existing migration needed to be alterted to avoid data loss. --------- Co-authored-by: delvh <[email protected]> Co-authored-by: Giteabot <[email protected]>
GiteaBot
added
the
lgtm/need 2
pull-request-size
bot
added
the
size/M
silverwind
approved these changes
Oct 8, 2023
GiteaBot
added
lgtm/need 1
denyskon
approved these changes
Oct 9, 2023
GiteaBot
added
lgtm/done
denyskon
added
the
skip-changelog
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport #27504 by @silverwind
Partial revert of #25839. This commit status is used by a number of external integrations, so I think we should not remove it (See #25839 (comment)). This is a rare case where an existing migration needed to be alterted to avoid data loss.