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

The use of dash (-) in repository names breaks cross-referencing in issues #1478

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

Originally created by @djelenc on GitHub (Jan 26, 2018).

  • Gitea version (or commit ref): 82a7b02
  • Git version: ?
  • Operating system: irrelevant
  • Database (use [x]): irrelevant
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes: see below
    • No
    • Not relevant

Description

When you try to cross-reference an issue in a repository whose name contains a dash (`-˙ symbol), the automatic referencing breaks.

See here:

Props to @lafriks for zeroing in the bug.

Originally created by @djelenc on GitHub (Jan 26, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 82a7b02 - Git version: ? - Operating system: irrelevant - Database (use `[x]`): irrelevant - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: see below - [ ] No - [ ] Not relevant ## Description When you try to cross-reference an issue in a repository whose name contains a dash (`-˙ symbol), the automatic referencing breaks. See here: * [Cross-referencing when dash is used does not work](https://try.gitea.io/ZeroNet/ZeroNet/issues/3#issuecomment-1889) * [Cross-referencing when dash is not used works](https://try.gitea.io/ZeroNet/ZeroNet/issues/3#issuecomment-1906) Props to @lafriks for zeroing in the bug.
GiteaMirror added the type/bug label 2025-11-02 04:02:02 -06:00
GiteaMirror commented 2025-11-02 04:02:03 -06:00
Author
Owner
Copy Link

@HenrikBengtsson commented on GitHub (Jan 26, 2018):

UPDATE 2018-01-26: For the issue in this comment, see Issue #3381 instead.

This appears to affect any URLs containing hyphens. For example, in Gitea 1.3.2 the following URL:

  • http://singularity.lbl.gov/install-linux#build-an-rpm-from-source

is rendered as http://singularity.lbl.gov/install-linux#build-an-rpm-from-source. A workaround is to use Markdown links, e.g.

  • [http://singularity.lbl.gov/install-linux#build-an-rpm-from-source](http://singularity.lbl.gov/install-linux#build-an-rpm-from-source)
@HenrikBengtsson commented on GitHub (Jan 26, 2018): UPDATE 2018-01-26: For the issue in this comment, see Issue #3381 instead. This appears to affect any URLs containing hyphens. For example, in Gitea 1.3.2 the following URL: * `http://singularity.lbl.gov/install-linux#build-an-rpm-from-source` is rendered as [http://singularity.lbl.gov/install-linux#build](http://singularity.lbl.gov/install-linux#build-an-rpm-from-source)-an-rpm-from-source. A workaround is to use Markdown links, e.g. * `[http://singularity.lbl.gov/install-linux#build-an-rpm-from-source](http://singularity.lbl.gov/install-linux#build-an-rpm-from-source)`
GiteaMirror commented 2025-11-02 04:02:03 -06:00
Author
Owner
Copy Link

@thehowl commented on GitHub (Jan 26, 2018):

That is an entirely different issue: to solve these once and for all, I already opened #3381

@thehowl commented on GitHub (Jan 26, 2018): That is an entirely different issue: to solve these once and for all, I already opened #3381
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#1478
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?