Starting issue text with issue reference "#<number> more text..." does not link issue #3971

New Issue

GiteaMirror · 2025-11-02T05:32:13-06:00

GiteaMirror commented

2025-11-02 05:32:13 -06:00

Originally created by @ghost on GitHub (Sep 17, 2019).

Gitea version (or commit ref): 1.9.3
Git version: 2.20.1
Operating system: debian buster
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes example here
- No
- Not relevant
Log gist:

Description

If I create an issue and start the text with an issue reference it will instead cause the rendered markdown to produce a header

#1 is my open issue

^ will not produce the link to issue number 1 but instead create a header entry in the markdown

Screenshots

Just to compare to github:

Originally created by @ghost on GitHub (Sep 17, 2019). - Gitea version (or commit ref): 1.9.3 - Git version: 2.20.1 - Operating system: debian buster - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes [example here](https://try.gitea.io/enckse/example/issues/2) - [ ] No - [ ] Not relevant - Log gist: ## Description If I create an issue and start the text with an issue reference it will instead cause the rendered markdown to produce a header ``` #1 is my open issue ``` ^ will not produce the link to issue number 1 but instead create a header entry in the markdown ## Screenshots ![Screenshot_2019-09-17 example](https://user-images.githubusercontent.com/1933941/65072991-f3634300-d95f-11e9-97e6-00eefc5e64ab.png) ![Screenshot_2019-09-17 example(1)](https://user-images.githubusercontent.com/1933941/65072998-f5c59d00-d95f-11e9-8547-e79e14806280.png) Just to compare to github: ![Screenshot_2019-09-17 go-gitea gitea](https://user-images.githubusercontent.com/1933941/65073086-1db50080-d960-11e9-8e47-d4a870831b6e.png) ![Screenshot_2019-09-17 go-gitea gitea(1)](https://user-images.githubusercontent.com/1933941/65073159-45a46400-d960-11e9-89df-30b2a85c361a.png)

GiteaMirror added the issue/confirmed type/bug labels 2025-11-02 05:32:13 -06:00

GiteaMirror closed this issue

2025-11-02 05:32:13 -06:00

GiteaMirror commented

2025-11-02 05:32:14 -06:00

@guillep2k commented on GitHub (Sep 17, 2019):

It is, however, the expected behavior, as # is a marker for a title. You can preceed the # with a space to "cheat" the marking:

#123  <--- It's a title
 #123 <--- It's not (it's a reference)

@guillep2k commented on GitHub (Sep 17, 2019): It is, however, the expected behavior, as `#` is a marker for a title. You can preceed the `#` with a space to "cheat" the marking: ``` #123 <--- It's a title #123 <--- It's not (it's a reference) ```

GiteaMirror commented

2025-11-02 05:32:14 -06:00

@lunny commented on GitHub (Sep 18, 2019):

This should be an execution order problem. Maybe we should replace the #123 before we render that as a markdown.

@lunny commented on GitHub (Sep 18, 2019): This should be an execution order problem. Maybe we should replace the `#123` before we render that as a markdown.

GiteaMirror commented

2025-11-02 05:32:14 -06:00

@stale[bot] commented on GitHub (Nov 17, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 17, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:32:14 -06:00

@ghost commented on GitHub (Nov 17, 2019):

Unless this has been fixed as a side-effect and not linked to this issue - it is still open.

@ghost commented on GitHub (Nov 17, 2019): Unless this has been fixed as a side-effect and not linked to this issue - it is still open.

GiteaMirror commented

2025-11-02 05:32:15 -06:00

@lunny commented on GitHub (Jan 17, 2020):

I think this has been fixed.

@lunny commented on GitHub (Jan 17, 2020): I think this has been fixed.

GiteaMirror referenced this issue

2025-11-02 12:28:23 -06:00