Skip to content

Add a config parameter to limit the number of active branches #84

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

Closed
jeremystretch opened this issue Sep 6, 2024 · 0 comments · Fixed by #100
Closed

Add a config parameter to limit the number of active branches #84

jeremystretch opened this issue Sep 6, 2024 · 0 comments · Fixed by #100
Assignees
Labels
type: feature A new feature or functionality
Milestone

Comments

@jeremystretch
Copy link
Contributor

Plugin Version

v0.4.0

Proposed functionality

Introduce a new configuration parameter (e.g. max_active_branches) to limit the permitted number of active (non-merged) branches. This would complement the max_branches parameter introduced in v0.4.0, which limits the total number of branches.

It might also make sense to introduce a per-user variant of this parameter.

Use case

It may be desirable to limit the number of active branches, either globally or on a per-user basis, to avoid the build-up of abandoned work. This parameter would allow an administrator to enforce a limit on active branches without constraining the total number of branches in the database.

External dependencies

No response

@jeremystretch jeremystretch added the type: feature A new feature or functionality label Sep 6, 2024
@jeremystretch jeremystretch added this to the v0.5 milestone Sep 9, 2024
@jeremystretch jeremystretch self-assigned this Sep 9, 2024
jeremystretch added a commit that referenced this issue Sep 12, 2024
* Closes #84: Introduce the max_active_branches parameter

* Rename max_active_branches to max_working_branches

* Update error message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature A new feature or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant