issue tags eg "#1" vs "someprefix#1" #3581

New Issue

GiteaMirror · 2025-11-02T05:17:58-06:00

GiteaMirror commented

2025-11-02 05:17:58 -06:00

Originally created by @flobee on GitHub (Jul 12, 2019).

Can you reproduce the bug at https://try.gitea.io:
https://try.gitea.io/company/commit-tags-problem/issues/2

Description

in this issue2 should not be marked within the commit which belongs to issue1
I think for a work around could be writing KB\#2 but feels uncomfortable and dont work. How to?

Kind regards

Originally created by @flobee on GitHub (Jul 12, 2019). - Can you reproduce the bug at https://try.gitea.io: https://try.gitea.io/company/commit-tags-problem/issues/2 ## Description in this issue2 should not be marked within the commit which belongs to issue1 I think for a work around could be writing `KB\#2` but feels uncomfortable and dont work. How to? Kind regards

GiteaMirror added the type/bug label 2025-11-02 05:17:58 -06:00

GiteaMirror closed this issue

2025-11-02 05:17:58 -06:00

GiteaMirror commented

2025-11-02 05:17:59 -06:00

@Cherrg commented on GitHub (Jul 12, 2019):

(Note: This does happen here on github too
e.g.: https://github.com/go-gitea/gitea/issues/6371 references to #(1-10))

@Cherrg commented on GitHub (Jul 12, 2019): (Note: This does happen here on github too e.g.: https://github.com/go-gitea/gitea/issues/6371 references to #(1-10))

GiteaMirror commented

2025-11-02 05:18:00 -06:00

@Cherrg commented on GitHub (Jul 12, 2019):

may it is possible to link commits only when there is a space or linestart before #

@Cherrg commented on GitHub (Jul 12, 2019): may it is possible to link commits only when there is a space or linestart before #

GiteaMirror commented

2025-11-02 05:18:00 -06:00

@mrsdizzie commented on GitHub (Jul 12, 2019):

Hmm yea it shouldn't be doing that, will look and send a fix

@mrsdizzie commented on GitHub (Jul 12, 2019): Hmm yea it shouldn't be doing that, will look and send a fix

GiteaMirror commented

2025-11-02 05:18:00 -06:00

@flobee commented on GitHub (Jul 17, 2019):

Is there an update script to update records from the past 👎 👍 ? It seems the content get static after a push was made :~/

@flobee commented on GitHub (Jul 17, 2019): Is there an update script to update records from the past :-1: :+1: ? It seems the content get static after a push was made :~/

GiteaMirror commented

2025-11-02 05:18:00 -06:00

@mrsdizzie commented on GitHub (Jul 17, 2019):

@flobee Unfortunately not as it wouldn't necessarily know what was added there for what reason.

You could manually remove them from the DB and you can find those type of mention comments like this:

SELECT * from comment WHERE type = 4;

Or you could search for the specific string in the example in this issue:

SELECT * from comment WHERE type = 4 AND content LIKE '%KB#%';

type 4 is a commit reference which is where this bug was

@mrsdizzie commented on GitHub (Jul 17, 2019): @flobee Unfortunately not as it wouldn't necessarily know what was added there for what reason. You could manually remove them from the DB and you can find those type of mention comments like this: ``` SELECT * from comment WHERE type = 4; ``` Or you could search for the specific string in the example in this issue: ``` SELECT * from comment WHERE type = 4 AND content LIKE '%KB#%'; ``` type 4 is a commit reference which is where this bug was

GiteaMirror commented

2025-11-02 05:18:01 -06:00

@flobee commented on GitHub (Jul 17, 2019):

thx!

@flobee commented on GitHub (Jul 17, 2019): thx!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3581