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

Autolinking commit hashes might break some links #2411

New Issue
Closed
opened 2025-11-02 04:35:07 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:35:07 -06:00
Owner
Copy Link

Originally created by @vbrandl on GitHub (Oct 15, 2018).

Description

When posting a link, that ends in something that could be a commit hash, the auto linking feature for commit hashes breaks the actual link. I tried with the link github.com/schemaorg/schemaorg/issues/1912#issuecomment-429827337 but Gitea will detect it as github.com/schemaorg/schemaorg/issues/1912#issuecomment, - and https://[gitea instance]/[user]/[repo]/commit/429827337. An example of this can be seen in https://try.gitea.io/foobar19/foobar-repo/issues/1.

This only happens for auto detected links. Using the Markdown link syntax []() produces a correct link.

Originally created by @vbrandl on GitHub (Oct 15, 2018). - Gitea version (or commit ref): 4090204 - Can you reproduce the bug at https://try.gitea.io: - [x] Yes https://try.gitea.io/foobar19/foobar-repo/issues/1 - [ ] No - [ ] Not relevant ## Description When posting a link, that ends in something that could be a commit hash, the auto linking feature for commit hashes breaks the actual link. I tried with the link [github.com/schemaorg/schemaorg/issues/1912#issuecomment-429827337](https://github.com/schemaorg/schemaorg/issues/1912#issuecomment-429827337) but Gitea will detect it as [github.com/schemaorg/schemaorg/issues/1912#issuecomment](https://github.com/schemaorg/schemaorg/issues/1912#issuecomment), `-` and [https://[gitea instance]/[user]/[repo]/commit/429827337](https://try.gitea.io/foobar19/foobar-repo/commit/429827337). An example of this can be seen in https://try.gitea.io/foobar19/foobar-repo/issues/1. This only happens for auto detected links. Using the Markdown link syntax `[]()` produces a correct link.
GiteaMirror added the issue/duplicate label 2025-11-02 04:35:07 -06:00
GiteaMirror commented 2025-11-02 04:35:08 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 15, 2018):

duplicated with #5047

@lunny commented on GitHub (Oct 15, 2018): duplicated with #5047
GiteaMirror commented 2025-11-02 04:35:09 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2018):

ditto with #4435

@ghost commented on GitHub (Oct 16, 2018): ditto with #4435
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 issue/duplicate
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#2411
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?