github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Order code comments by review #2018

New Issue
Closed
opened 2025-11-02 04:21:23 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:21:23 -06:00
Owner
Copy Link

Originally created by @jonasfranz on GitHub (Jul 6, 2018).

It would be nice if code comments will be ordered by Review > Date. This will have the side-effect that we can show the complete conversation in the "conversations" tab. At the moment only the first comment of line gets shown at reviews in conversation tab.

My idea would be to introduce a new column at comment called reply_to containing the review id of the reply.

Blocked by #3748

Originally created by @jonasfranz on GitHub (Jul 6, 2018). It would be nice if code comments will be ordered by Review > Date. This will have the side-effect that we can show the complete conversation in the "conversations" tab. At the moment only the first comment of line gets shown at reviews in conversation tab. My idea would be to introduce a new column at `comment` called `reply_to` containing the review id of the reply. Blocked by #3748
GiteaMirror added the type/enhancement label 2025-11-02 04:21:23 -06:00
GiteaMirror commented 2025-11-02 04:21:24 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Aug 6, 2018):

#3748 got implemented! Ready to get implemented.

@jonasfranz commented on GitHub (Aug 6, 2018): #3748 got implemented! Ready to get implemented.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2018
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?