Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues related commit activity (reference) is missing #7968

Closed
davydov-vyacheslav opened this issue Aug 25, 2019 · 9 comments
Closed

Issues related commit activity (reference) is missing #7968

davydov-vyacheslav opened this issue Aug 25, 2019 · 9 comments

Comments

@davydov-vyacheslav
Copy link

  • 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:
Снимок экрана 2019-08-25 в 10 09 07

Now looks like it missed:
Снимок экрана 2019-08-25 в 10 01 59

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

Is there a way to get this feature back?

@mrsdizzie
Copy link
Member

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.

@davydov-vyacheslav
Copy link
Author

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

@mrsdizzie
Copy link
Member

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

@davydov-vyacheslav
Copy link
Author

@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?

@mrsdizzie
Copy link
Member

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

@davydov-vyacheslav
Copy link
Author

Is there a way to prioritize the issue?

@mrsdizzie
Copy link
Member

#8101 should fix this particular case when it is done I believe

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Nov 4, 2019
@lunny
Copy link
Member

lunny commented Nov 5, 2019

Should be closed by #8101

@lunny lunny closed this as completed Nov 5, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants