Change default initial branch to match github

[davisagli]

Fixes #59

Tested on my machine with and without init.defaultBranch set in ~/.gitconfig

[rohnsha0]

for me it still follows the ~/.gitconfig's defaultBranch

[davisagli]

@rohnsha0 Yes, that is my goal: use init.defaultBranch from ~/.gitconfig if it is set (because that is the user's explicit preference). But if it isn't specified there, then use main instead of master.

[rohnsha0]

@rohnsha0 Yes, that is my goal: use init.defaultBranch from ~/.gitconfig if it is set (because that is the user's explicit preference). But if it isn't specified there, then use main instead of master.

ummm, to my surprise. When I removed the init.defaultBranch it was still using the master branch... But looking it it again and wait for others to response!

[stevepiercy]

I have no idea how to run a local checkout of this branch to verify it works. It's not covered in the README, and I lack familiarity with the tooling. @davisagli can you clue me in?

[davisagli]

@stevepiercy make install, then hatch run cookieplone

[rohnsha0]

lgtm

[stevepiercy]

@davisagli FTR yesterday after make install, I tried pipx run cookieplone project and python3 -m cookieplone project. Can you push a commit to add hatch run cookieplone to the README after Setup and a heading "Run Cookieplone with your changes" or something like that while I test?

[stevepiercy]

This might be a new issue, but I tried this:

  [7/17] Should we use prerelease versions? (No): Y
  [8/17] Plone Version (6.0.14): 

I expected 6.1.0rc1.

[davisagli]

@stevepiercy not new, you just ran into #47

[stevepiercy]

Confirming the change works with init:

$ git status  
On branch oogah-boogah

...and without.

$ git status
On branch main

So the change works for me, too.

[stevepiercy]

It would be good to add a commit for the README, as I mentioned in #60 (comment), but I won't hold this up for merging. Thank you!

[stevepiercy]

README snippet added in c499c51

[davisagli]

Thanks @stevepiercy