Closed targos closed 3 years ago
main
and resolve conflicts post-merge of this PR.There may be tools referencing the master
branch directly. If GitHub does not automatically redirect pulls from master such that they pull from main automatically (akin to HTTP 301), then on the master branch only, there may be a need for an informational post-pull git hook and README notice to inform users of the rename/deprecation.
Changed the links to use HEAD
.
@targos I pushed a main
branch from https://github.com/nodejs/release-keys/commit/d7dd5221e4286e01ea0e6046e4b4190628f5d9af just now, which matches the commit ref for master
as well. I do not have privileges to set the default branch on this repo, so FYI should be ready to swap for anyone with the capability to edit that.
I just renamed the branch 👍🏻
I'll do the actual renaming right before this is merged.