-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Reference issue from pull request #3134
Comments
Also, referencing an issue, ie., |
Can you create sample on try.gitea.io to demonstrate this problem |
@lafriks - sure! Issue to issue ref: 1: https://try.gitea.io/svarlamov/sample-issues-3134/issues/1 2 references 1, but there's nothing in 1 to show that (as there would be for a commit msg) PR to issue ref: PR(a): https://try.gitea.io/svarlamov/sample-issues-3134/pulls/3 PR(a) references ISSUE(b), however, there's nothing to indicate that in ISSUE(b) -- as there otherwise would be for a commit msg |
I think @svarlamov means reference comments. |
i think he means an information like the fourth under this comment in a pull request here. |
and like the one below that. :-) |
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. |
@lunny Perhaps the stale bot should be configured to ignore issues that are tracked in a milestone, or another tag could be created to exempt an issue from auto-closing. It's not exactly ideal to keep bumping them manually. |
there is already label |
+1 for linking back to the PR from the issue view. But also, it'd be nice to be able to close issues from PR descriptions. I.e. if the reference is "closes #123" it would close issue number 123 once the PR is merged (same as from commits). I do this all the time on GitHub and kind of miss it on Gitea now. |
This is pending. I'm interested in this feature, I might work on it next. Any caveats I should be aware of? |
@skddc One thing at a time ;-) make a new issue on that one (It's probably somewhere already!) please @guillep2k Thanks! |
Description
When referencing an issue from a pull request description, ie.,
targeting #125
links properly, but when you're in the issue, there's no message saying that it was referenced in a pull request (such as Gitea does with commit messages or the way that Github does with pull request descriptions)The text was updated successfully, but these errors were encountered: