Refactor view issue & comment list styles#35061
Merged
wxiaoguang merged 1 commit intogo-gitea:mainfrom Jul 13, 2025
Merged
Conversation
Contributor
Author
lunny
approved these changes
Jul 13, 2025
delvh
approved these changes
Jul 13, 2025
hiifong
approved these changes
Jul 13, 2025
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Jul 14, 2025
* giteaofficial/main: Refactor view issue & comment list styles (go-gitea#35061) Fix user's sign email check (go-gitea#35045) [skip ci] Updated translations via Crowdin Fix incorrect comment diff hunk parsing, fix github asset ID nil panic (go-gitea#35046) Add Notifications section in User Settings (go-gitea#35008)
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.
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.






The copy-paste code caused various problems, this PR fixes all and make the code maintainable.
There might be some small UI regressions that I didn't found, while these should be easy to fix, indeed we have clearer code
Fix #35060