-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Reference" section to Issue view sidebar #19609
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you for your first contribution!
Nevermind, not part of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally L-G-T-M
I would suggest to remove the ReferenceLink
(I can take the work if no objection).
(just mark it as requested changes
to prevent to be merged too soon.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution! Let's wait for the CI pass, then get it merged. 🎉
. |
* giteaofficial/main: Simplify `IsVendor` (go-gitea#19626) Prevent NPE when checking repo units if the user is nil (go-gitea#19625) Skip duplicated layers. (go-gitea#19624) Add "Reference" section to Issue view sidebar (go-gitea#19609) GetFeeds must always discard actions with dangling repo_id (go-gitea#19598)
* Add "Reference" section to Issue view sidebar * Removed unneeded tailored CSS, added Fomantic UI classes * Removed tailored CSS in favour of HTML-only approach Kindly provided by @Gusted * Added i18 translation key for reference link string * Corrected spelling of "References:" to "Reference:" for reference link text * Removed `Issue.ReferenceLink` in favour of a local template variable
Add a "References..." item to the sidebar when viewing an issue in a repository.
More detail can be found in #19608 , with examples of existing functionality.
Here is an example (when the project has been built):