Closing issues via commit on non-default branch #2857

New Issue

GiteaMirror · 2025-11-02T04:51:40-06:00

GiteaMirror commented

2025-11-02 04:51:40 -06:00

Originally created by @s-hamann on GitHub (Feb 4, 2019).

Gitea version (or commit ref): 1.7.0

Description

While I do understand the reasoning behind #5622 this breaks out workflow here. We keep a stable default (master) branch and do the development on a dev branch. We close issues when they are fixed on the dev branch and use milestones to keep track of what needs to be done before the next release/merge to master.

I believe our development model is not so uncommon that #5622 would not affect a few other teams as well.
Could the auto-closing behaviour somehow be enabled for additional branches, not only for the default branch?

Originally created by @s-hamann on GitHub (Feb 4, 2019). - Gitea version (or commit ref): 1.7.0 ## Description While I do understand the reasoning behind #5622 this breaks out workflow here. We keep a stable default (master) branch and do the development on a dev branch. We close issues when they are fixed on the dev branch and use milestones to keep track of what needs to be done before the next release/merge to master. I believe our development model is not so uncommon that #5622 would not affect a few other teams as well. Could the auto-closing behaviour somehow be enabled for additional branches, not only for the default branch?

GiteaMirror added the type/enhancement label 2025-11-02 04:51:40 -06:00

GiteaMirror closed this issue

2025-11-02 04:51:40 -06:00

GiteaMirror commented

2025-11-02 04:51:41 -06:00

@lafriks commented on GitHub (Feb 4, 2019):

This should probably be added as an option to repository to allow change branch when issues are closed automatically

@lafriks commented on GitHub (Feb 4, 2019): This should probably be added as an option to repository to allow change branch when issues are closed automatically

GiteaMirror commented

2025-11-02 04:51:41 -06:00

@lunny commented on GitHub (Feb 6, 2019):

I added a break label on #5622 and some one could send a pull request to add a config to enable closing issues via commit on non-default branch.

@lunny commented on GitHub (Feb 6, 2019): I added a break label on #5622 and some one could send a pull request to add a config to enable closing issues via commit on non-default branch.

GiteaMirror referenced this issue

2025-11-02 12:15:11 -06:00

[PR #2859] [MERGED] Fix click create pull request button 404 #16636

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