Fix incorrect ref commit ID usage#33331
Merged
Merged
Conversation
Contributor
Author
|
Related pages: |
0f47c8c to
3628faa
Compare
lunny
approved these changes
Jan 20, 2025
Zettat123
approved these changes
Jan 20, 2025
Co-authored-by: Zettat123 <zettat123@gmail.com>
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Jan 21, 2025
* giteaofficial/main: [skip ci] Updated translations via Crowdin Fix incorrect ref commit ID usage (go-gitea#33331) Improve sync fork behavior (go-gitea#33319) Refactor response writer & access logger (go-gitea#33323)
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
After the RefName refactoring, the
ctx.Repo.CommitIDis only set when there is aRepoRefByTypemiddleware.Many handlers do not use that middleware and they only use "default branch"