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

@User in commit message (description) #1276

New Issue
Closed
opened 2025-11-02 03:55:06 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 03:55:06 -06:00
Owner
Copy Link

Originally created by @SohnyBohny on GitHub (Nov 24, 2017).

if you add @User in commit message (description) it won't be blue like in "normal" text areas

Is it a bug or a feature?

Originally created by @SohnyBohny on GitHub (Nov 24, 2017). if you add @User in commit message (description) it won't be blue like in "normal" text areas Is it a bug or a feature?
GiteaMirror added the type/feature label 2025-11-02 03:55:06 -06:00
GiteaMirror commented 2025-11-02 03:55:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 25, 2017):

@SohnyBohny any screenshots or example on https://try.gitea.io ?

@lunny commented on GitHub (Nov 25, 2017): @SohnyBohny any screenshots or example on https://try.gitea.io ?
GiteaMirror commented 2025-11-02 03:55:07 -06:00
Author
Owner
Copy Link

@SohnyBohny commented on GitHub (Nov 25, 2017):

Screenshot 1
Screenshot 2

The red underlined part in the second screenshot should be blue and clickable

@SohnyBohny commented on GitHub (Nov 25, 2017): ![Screenshot 1](https://user-images.githubusercontent.com/10254103/33230979-7d29b83e-d1ed-11e7-871f-b5fee1dac07b.png) ![Screenshot 2](https://user-images.githubusercontent.com/10254103/33231025-42761344-d1ee-11e7-92dd-ab7c05b6a0b1.png) The red underlined part in the second screenshot should be blue and clickable
GiteaMirror commented 2025-11-02 03:55:08 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 25, 2017):

I think this should be a new feature.

@lunny commented on GitHub (Nov 25, 2017): I think this should be a new feature.
GiteaMirror commented 2025-11-02 03:55:08 -06:00
Author
Owner
Copy Link

@svarlamov commented on GitHub (Nov 30, 2017):

I was considering creating a new issue, but since the implementation of this seems to be ubiquitous, I will post my thoughts here. This sort of @ mention feature should also show a dropdown of users. There are too many people to remember everyone's username. It would be really helpful to have the Github-style inline auto-complete suggestions when you type the '@'. I'm sure that this is probably something that we can simply add into the HTML templates for issues, and the other related text areas.

@svarlamov commented on GitHub (Nov 30, 2017): I was considering creating a new issue, but since the implementation of this seems to be ubiquitous, I will post my thoughts here. This sort of @ mention feature should also show a dropdown of users. There are too many people to remember everyone's username. It would be really helpful to have the Github-style inline auto-complete suggestions when you type the '@'. I'm sure that this is probably something that we can simply add into the HTML templates for issues, and the other related text areas.
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/feature
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#1276
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?