Closed szabgab closed 3 years ago
You have to set git config init.defaultBranch
to master
.
Doing that globally git config --global init.defaultBranch master
fixes the problems, but that does not feel right. Why should one repository have an impact on my global git configuration.
Unfortunately doing it locally git config --local init.defaultBranch master
did not help.
Why is this needed?
It seems git changed the default branch name configuration. This breaks shards' specs because they expect it to be master
.
A local change does not help because the spec suite creates new git repositories and they would inherit the default / global config.
Git has changed and AFAIK now each one of us have to manually decided what is our default branch and we have to configure it. So I had "main" configured.
IMHO neither shard nor the tests should assume what is the globally configured default branch for the particular user.
I wanted to contribute a few test-cases so I cloned the shards repository ran
make
that was successful then I ranmake test
and got several exceptions:How can I ran the tests?