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

Links for commit hashes ending in comma are not rendered #6617

New Issue
Closed
opened 2025-11-02 07:01:36 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 07:01:36 -06:00
Owner
Copy Link

Originally created by @nuno-silva on GitHub (Jan 3, 2021).

Description

When leaving an issue comment containing valid commit hashes, those are not recognised if they are followed by a comma (,).
A workaround is to leave a space between the hash and the comma, but you need to remember to do it when writing the comment or go back and edit it after noticing the commit link was not rendered.
Dots are accepted though. See the screenshot for reference.

Unless there was a specific reason for not accepting commas, this is an easy fix.
I will prepare a pull request in a bit.

Screenshots

raw text rendered text

Originally created by @nuno-silva on GitHub (Jan 3, 2021). - Gitea version (or commit ref): 1.14.0+dev-499-g7576e37a6 - Git version: NA - Operating system: NA - Database: NA - Can you reproduce the bug at https://try.gitea.io: - [x] Yes https://try.gitea.io/nuno-silva/test/issues/8 - [ ] No ## Description When leaving an issue comment containing valid commit hashes, those are not recognised if they are followed by a comma (`,`). A workaround is to leave a space between the hash and the comma, but you need to remember to do it when writing the comment or go back and edit it after noticing the commit link was not rendered. Dots are accepted though. See the screenshot for reference. Unless there was a specific reason for not accepting commas, this is an easy fix. I will prepare a pull request in a bit. ## Screenshots ![raw text](https://user-images.githubusercontent.com/6935057/103478597-abb83300-4dbf-11eb-93f1-6d45764e1ef3.png) ![rendered text](https://user-images.githubusercontent.com/6935057/103478468-d48bf880-4dbe-11eb-9cb8-0857259b8965.png)
GiteaMirror added the type/bug label 2025-11-02 07:01:36 -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/bug
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#6617
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?