You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
GitHub announced that new repositories will use
main
instead ofmaster
as the default branch starting on October 1, 2020. The default branch handled by this plugin ismaster
. To make a migration to the naming strategy easier, the default value forgit.requireBranch
should bemaster
andmain
. While I understand that the value is configurable, long-term there needs to be a change to the plugin code to avoid having to definemain
over an over again in consuming projects.The text was updated successfully, but these errors were encountered: