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

The requireBranch should support "main" as default value #340

Open
bmuschko opened this issue Sep 21, 2020 · 2 comments
Open

The requireBranch should support "main" as default value #340

bmuschko opened this issue Sep 21, 2020 · 2 comments

Comments

@bmuschko
Copy link

GitHub announced that new repositories will use main instead of master as the default branch starting on October 1, 2020. The default branch handled by this plugin is master. To make a migration to the naming strategy easier, the default value for git.requireBranch should be master and main. While I understand that the value is configurable, long-term there needs to be a change to the plugin code to avoid having to define main over an over again in consuming projects.

@bmuschko
Copy link
Author

bmuschko commented Oct 1, 2020

Ping! Are there plans to support this?

@jan-xyz
Copy link

jan-xyz commented Jul 30, 2021

We just ran into this problem on a larger scale in all our internal projects. All gradle projects failed releasing afterwards because it wasn't a simple rename but actually a default value that now needed to be adjusted. I think it would help lots of teams if both branch names are supported. It is highly unlikely that a code-base has both names and you only want to release on one of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants