Closed zzarne closed 2 years ago
I was going to propose the same, and ask the same.
Would clones be able to pull afterwards without issues, without any changes on their side?
Issue #16 is about a feature that isn't present in the current default version. Users could keep using freedb/gnudb if it is that important to them.
Would clones be able to pull afterwards without issues, without any changes on their side?
As long as we don't rename the 'master' branch, existing clones would pull from the same branch as before. New clones would get the new default branch, which would be 'main', i.e. Python 3. So we won't rename the 'master' branch in the near future.
Maybe you can update the repository "About" description with hints about the meaning of the branches. I remember it took a while to figure out the python3 version is in a separate branch...
It appears the default can be set using the web interface: https://github.com/jack-cli-cd-ripper/jack/settings/branches
Switched branches using the web interface. Closing.
I want to discuss two issues here:
I think we are ready, but maybe we want to fix #16 first.
I've never done this, but it should be as simple as
and then change the default branch in github Settings->Branches to main.
We then could rename the master branch to e.g. python2 to avoid confusion.
What do you say? Comments welcome.