-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
closing issues via commit on non-default branch #2314
Comments
@lafriks I think this is a feature not a bug. |
@lunny I would call it undesired behaviour :) so it is somewhere in between :) |
|
would consider this as bug, closing issue via commit in a feature branch should not be possible |
HarshitOnGitHub
added a commit
to HarshitOnGitHub/gitea
that referenced
this issue
Jan 3, 2019
Adds a small check to close the issues only if the referencing commits are on the default branch. Fixes: go-gitea#2314.
lafriks
pushed a commit
that referenced
this issue
Jan 4, 2019
Adds a small check to close the issues only if the referencing commits are on the default branch. Fixes: #2314.
HarshitOnGitHub
added a commit
to HarshitOnGitHub/gitea
that referenced
this issue
Jan 5, 2019
Adds a small check to close the issues only if the referencing commits are on the default branch. Fixes: go-gitea#2314.
lafriks
pushed a commit
that referenced
this issue
Jan 5, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
it's possible to close issues via commit message by pushing to a non-default branch, expected behavior should be that an issue only closes on commits on default branch (master). this is important for code reviewing workflows, where the code-reviewer megres/rebases a feature branch to master.
related: gogs/gogs#4699
The text was updated successfully, but these errors were encountered: