Default branch main instead of master

[olanod]

On a freshly created project from github I ran the version command and got error: not allowed to run on branch main because it doesn't match pattern master. Since it will be the default from now on could main be the default instead of master or have both as allowed branches?

[pksunkara]

There are quite a few legacy projects which use master and also sometimes new projects that are used with legacy tools. I think #14 once implemented will solve this issue.

[XAMPPRocky]

Hey, I think cargo-workspaces should allow both main and master by default, so that it can work with both new projects and legacy projects, and very rarely would a project ever have both at the same time. I don't consider #14 to be a solution, as I don't want to have to create a config file for this tool in every project I maintain, just to use the new default naming.

[pksunkara]

I use https://docs.rs/glob/0.3.0/glob/struct.Pattern.html to match the branch name with a pattern. Unfortunately it doesn't seem like it's possible to provide master|main as the default pattern because the crate doesn't seem to support OR. Any idea on how to proceed?

https://github.com/pksunkara/cargo-workspaces/blob/master/cargo-workspaces/src/utils/git.rs#L96

[XAMPPRocky]

I think the simplest solution would be to change allow_branch to be Option<String> so that you can detect its presence by a user, and if not given a value, just try both patterns (one after the other) and error if it matches neither.

[pksunkara]

5fa9ae5 should work if anyone wants to test.