Option to choose branches while running installation scripts.

[charliie-dev]

Propose: as title.

Motivation: Current setting is sufficient enough for average users. However, when it comes to the time of migrating to a newer nvim version or a large to-be-tested patch-branch, an option to choose branches is quite convenient. Personally I used to do a full rundown on our installation scripts to test if there's anything weird.

prototype code:

curl -L https://api.github.com/repos/ayamir/nvimdots/branches | jq '.[].name'

curl -L https://api.github.com/repos/ayamir/nvimdots/branches | grep name

btw my grep is an alias to ugrep

Original discussion:
#674 (comment)
#674 (comment)

cc @ayamir @Jint-lzxy if u guys think it's worthy to add. I'll do a PR when I got time.

[Jint-lzxy]

Some thoughts (taken from #674 (comment)):

I can't think of a reason why we should implement this - FWIW branch detection based on nvim --version would suffice.
In fact, if ppl really want to customize their clone branch, CCLONE_BRANCH is reserved as a global option for them:

nvimdots/scripts/install.ps1

Line 22 in f1c5f09

$env:CCLONE_BRANCH ??= 'main'

[charliie-dev]

Some thoughts (taken from #674 (comment)):

I can't think of a reason why we should implement this - FWIW branch detection based on nvim --version would suffice.

In fact, if ppl really want to customize their clone branch, CCLONE_BRANCH is reserved as a global option for them:

nvimdots/scripts/install.ps1

Line 22 in f1c5f09

$env:CCLONE_BRANCH ??= 'main'

i just realized what u mean lol, and yes that should work!

[charliie-dev]

Just tested it. Setting pwsh env var indeed works fine!