Use correct branch for .editorconfig error #21152
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
silverwind
approved these changes
Sep 14, 2022
GiteaBot
added
the
lgtm/need 1
lunny
approved these changes
Sep 14, 2022
GiteaBot
added
lgtm/done
lunny
added
the
skip-changelog
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Sep 15, 2022
* upstream/main: Display image digest for container packages (go-gitea#21170) Use correct branch for .editorconfig error (go-gitea#21152) Passing command line arguments correctly by string slice (go-gitea#21168) Sort branches and tags by date descending (go-gitea#21136) Skip dirty check for team forms (go-gitea#21154) Add KaTeX rendering to Markdown. (go-gitea#20571)
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.
In #21088 I accidentally forgot to support multiple branches. It always checks the default branch, no matter on which branch you are working on. With this fix, it always shows the error from the current branch. Sorry for that.