github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Issue ref lines could be improved #10573

New Issue
Open
opened 2025-11-02 09:11:37 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 09:11:37 -06:00
Owner
Copy Link

Originally created by @wiktor-k on GitHub (Mar 31, 2023).

Feature Description

I'm using issue refs as pointers to for example fix release etc and I've noticed they could be improved in several ways with regard to "clickability".

It's hard to visualise without hover effect but if you look at my sample issue:

2023-03-31-12-12-21

The "wiktor referenced this issue 12 seconds ago" line has everything clickable, 3 links, very nice.

Compare that with the ref line: "wiktor changed reference from refs/tags/v0.1.16 to refs/tags/v0.1.15 now" only nick is clickable.

Improvements possible:

  • refs in bold should be clickable, if they are refs to tags take the user to tag view, if they are to branch take the user to branch tag,
  • timestamp should be clickable just like in the "issue ref" case.

I'd be happy to work on this if you think my proposal is OK. If you have better suggestions I'm all ears too :)

Screenshots

No response

Originally created by @wiktor-k on GitHub (Mar 31, 2023). ### Feature Description I'm using issue refs as pointers to for example fix release etc and I've noticed they could be improved in several ways with regard to "clickability". It's hard to visualise without hover effect but if you [look at my sample issue](https://try.gitea.io/wiktor/pysequoia/issues/1): ![2023-03-31-12-12-21](https://user-images.githubusercontent.com/1718963/229092663-06a92841-8693-4b1a-bbdc-24fa97ab4b2d.png) The "[wiktor](https://try.gitea.io/wiktor) [referenced this issue ](https://try.gitea.io/wiktor/pysequoia/issues/2#issuecomment-165812)[12 seconds ago](https://try.gitea.io/wiktor/pysequoia/issues/1#event-165813)" line has everything clickable, 3 links, very nice. Compare that with the ref line: "[wiktor](https://try.gitea.io/wiktor) changed reference from refs/tags/v0.1.16 to refs/tags/v0.1.15 now" only nick is clickable. Improvements possible: - refs in bold should be clickable, if they are refs to tags take the user to tag view, if they are to branch take the user to branch tag, - timestamp should be clickable just like in the "issue ref" case. I'd be happy to work on this if you think my proposal is OK. If you have better suggestions I'm all ears too :) ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 09:11:37 -06:00
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/proposal
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#10573
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?