Rename primary branch to main

[mhdawson]

We are going through all of the node.js repositories to rename the primary branch to main. Please see nodejs/node#33864 for more context.

There might be a number of places we need to change jobs that use the build repo (although maybe if we use the default branch it might just be ok).

I think to start we should try to capture in this issue what might breach if we rename the default branch and then go from there.

[mhdawson]

The clone in the regular ci jobs I think will be ok (for example - https://ci.nodejs.org/job/node-test-commit-linuxone/configure). It is as follows:

git clone https://github.com/nodejs/build.git

which should still be ok if the default is renamed.

[mhdawson]

@richardlau, myself and @sxa looked at this today. The main dependency is on build jobs which pull files from the build repo. Those we believe will all be handled by the github redirects.

We will update those over time but because of the redirects is lower risk to just leave in place and do incrementally.

@nodejs/build FYI you will need to need to retarget their pushes to main going forward. These are the notes GitHub provided when we renamed:

git branch -m master <BRANCH>
git fetch origin
git branch -u origin/<BRANCH> <BRANCH>
git remote set-head origin -a

We added a branch protection rule that should prevent future pushes to master.

[richardlau]

Had to update some references in the Windows CI jobs where master was being assigned to a SCRIPTS_BRANCH environment variable and used in the build scripts..

Refs: https://github.com/nodejs/jenkins-config-test/commit/49c292378c3daa7cefea7c2f12b0e08658ce6c6c

build/jenkins/scripts/windows/ci-run.cmd

Line 14 in 0e963e3

git fetch --prune --no-tags https://github.com/%SCRIPTS_REPO%.git +refs/heads/%SCRIPTS_BRANCH%:refs/remotes/jenkins_tmp

[richardlau]

Haven't seen or been made aware of any other issues apart from the broken (now fixed) Windows CI so believe this is done.

[richardlau]

nodejs/node#43261 (comment)

Not sure why neither the GitHub widget nor the nodejs-github-bot are picking up the fact that there's been more recent Jenkins runs

I took a look at https://ci.nodejs.org/job/post-build-status-update/ and it is very red. The job was specifying to run the pipeline file from master, I've updated it to main https://github.com/nodejs/jenkins-config-test/commit/08ffb5c0ad3c76f1854450e84f1717fc387a646b (this seems a very big diff for a one word change 🤷 ).

The confusing thing is there were some successful runs about an hour ago so it can't be entirely the branch rename as that happened two weeks ago.