Issues related commit activity (reference) is missing #3837

New Issue

GiteaMirror · 2025-11-02T05:27:43-06:00

GiteaMirror commented

2025-11-02 05:27:43 -06:00

Originally created by @davydov-vyacheslav on GitHub (Aug 25, 2019).

Gitea version (or commit ref): 1.10.0+dev-189-g08c63190c
Reproducible on https://gitea.com

Description

Somewhere in time, there is was an feature of issues mention /reference like this:

Now looks like it missed:

The link to the issue is: https://gitea.com/davs/testrepo/issues/1

Is there a way to get this feature back?

Originally created by @davydov-vyacheslav on GitHub (Aug 25, 2019). - Gitea version (or commit ref): 1.10.0+dev-189-g08c63190c - Reproducible on https://gitea.com ## Description Somewhere in time, there is was an feature of issues mention /reference like this: <img width="881" alt="Снимок экрана 2019-08-25 в 10 09 07" src="https://user-images.githubusercontent.com/9931946/63646754-8c67bb00-c720-11e9-8778-4283446977b7.png"> Now looks like it missed: <img width="1207" alt="Снимок экрана 2019-08-25 в 10 01 59" src="https://user-images.githubusercontent.com/9931946/63646753-8c67bb00-c720-11e9-88b1-91763796ebee.png"> The link to the issue is: https://gitea.com/davs/testrepo/issues/1 Is there a way to get this feature back?

GiteaMirror added the issue/stale label 2025-11-02 05:27:43 -06:00

GiteaMirror closed this issue

2025-11-02 05:27:44 -06:00

GiteaMirror commented

2025-11-02 05:27:45 -06:00

@mrsdizzie commented on GitHub (Aug 26, 2019):

In your examples of it not working, it is because you have a colon after the #1 -- Gitea doesn't support that. It should either be blank, or the issue can be inside of square brackets or paren but #1:wouldn't be seen as a valid issue number in this case

Your working example appears to have a space between the issue number and colon which is why it works.

Perhaps a colon could be added. Github seem to support that and we try to match what they do, though it is not documented so hard to get everything always. That is why it isn't working in this case though, the feature hasn't gone away.

@mrsdizzie commented on GitHub (Aug 26, 2019): In your examples of it not working, it is because you have a colon after the ```#1``` -- Gitea doesn't support that. It should either be blank, or the issue can be inside of square brackets or paren but ```#1:```wouldn't be seen as a valid issue number in this case Your working example appears to have a space between the issue number and colon which is why it works. Perhaps a colon could be added. Github seem to support that and we try to match what they do, though it is not documented so hard to get everything always. That is why it isn't working in this case though, the feature hasn't gone away.

GiteaMirror commented

2025-11-02 05:27:45 -06:00

@davydov-vyacheslav commented on GitHub (Aug 26, 2019):

Ok. Got it. Just one comment: why “Fixed” has been determined and the issue has been closed after pushing the commits?

@davydov-vyacheslav commented on GitHub (Aug 26, 2019): Ok. Got it. Just one comment: why “Fixed” has been determined and the issue has been closed after pushing the commits?

GiteaMirror commented

2025-11-02 05:27:45 -06:00

@mrsdizzie commented on GitHub (Aug 26, 2019):

I'm not quite sure what you are asking sorry.

Are you asking why an issue is closed if you make a commit that says "fixed #1" ? If so that is based on:

https://help.github.com/en/articles/closing-issues-using-keywords

@mrsdizzie commented on GitHub (Aug 26, 2019): I'm not quite sure what you are asking sorry. Are you asking why an issue is closed if you make a commit that says "fixed #1" ? If so that is based on: https://help.github.com/en/articles/closing-issues-using-keywords

GiteaMirror commented

2025-11-02 05:27:45 -06:00

@davydov-vyacheslav commented on GitHub (Aug 26, 2019):

@mrsdizzie but according to the image, the colon is just after the issue number. And it works for closing the issue, but not works to make reference. That was the just confusion of logic difference.

Anyway, the answer of how it was worked has been obtained. Thank you.

Should I close the issue or it’d be the reference for further someone’s PR?

@davydov-vyacheslav commented on GitHub (Aug 26, 2019): @mrsdizzie but according to the image, the colon is just after the issue number. And it works for closing the issue, but not works to make reference. That was the just confusion of logic difference. Anyway, the answer of how it was worked has been obtained. Thank you. Should I close the issue or it’d be the reference for further someone’s PR?

GiteaMirror commented

2025-11-02 05:27:45 -06:00

@mrsdizzie commented on GitHub (Aug 26, 2019):

Ah OK I see what you mean thank you for the extra explanation -- I hadn't realized from the screenshots that the issue was closed by that commit but not quoted.

That is a bug you can leave this issue open for reference in PR thanks

@mrsdizzie commented on GitHub (Aug 26, 2019): Ah OK I see what you mean thank you for the extra explanation -- I hadn't realized from the screenshots that the issue was closed by that commit but not quoted. That is a bug you can leave this issue open for reference in PR thanks

GiteaMirror commented

2025-11-02 05:27:46 -06:00

@davydov-vyacheslav commented on GitHub (Sep 5, 2019):

Is there a way to prioritize the issue?

@davydov-vyacheslav commented on GitHub (Sep 5, 2019): Is there a way to prioritize the issue?

GiteaMirror commented

2025-11-02 05:27:46 -06:00

@mrsdizzie commented on GitHub (Sep 5, 2019):

https://github.com/go-gitea/gitea/pull/8101 should fix this particular case when it is done I believe

@mrsdizzie commented on GitHub (Sep 5, 2019): https://github.com/go-gitea/gitea/pull/8101 should fix this particular case when it is done I believe

GiteaMirror commented

2025-11-02 05:27:46 -06:00

@stale[bot] commented on GitHub (Nov 4, 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 4, 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:27:47 -06:00

@lunny commented on GitHub (Nov 5, 2019):

Should be closed by #8101

@lunny commented on GitHub (Nov 5, 2019): Should be closed by #8101

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#3837