This is a breaking change, I would rather tackle it in a way that would keep backwards compatibility.

Additionally, I think the behaviour you are trying to achieve could be done using

Thanks @pjbgf, yes it is indeed breaking, although it might be considered as breaking to align with changes to git client itself. I understand you have many downstreams you need to consider so I won't advocate for this breaking change past what I have already done.

Sadly, I had also considered the config setting, but the specific issue I am facing can't be set by the default branch config setting. The Init() function: https://github.com/go-git/go-git/blob/master/repository.go#L92 hardcodes master branch when creating a new repo.

I'd be happy to contribute a PR, perhaps to add a similar function, InitWithBranch, where Init would alias to that function but pass in the default of master?

Something like:

func Init(s storage.Storer, worktree billy.Filesystem) (*Repository, error) {
    InitWithBranch(s, worktree, plumbing.Master)
}
func InitWithBranch(s storage.Storer, worktree billy.Filesystem, branch string) (*Repository, error) {
// ...
h := plumbing.NewSymbolicReference(plumbing.HEAD, branch)
// ...

@techknowlogick apologies for the delay. Happy to review a PR on extending Init to support other default branches. I would just make sure you follow the naming convention we use and call it InitWithOptions.

Thanks for that suggestion re: existing conventions @pjbgf. I have submitted #764, which is hopefully more suitable :)