Chore: migrate master to main

[niteshseram]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain:
Migrate branch from master to main

What changes did you make? (Give an overview)

I have updated the occurrence of word master to main in GitHub action, Makefile.js and some docs
Closes #15042

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Nitesh Seram (6a37dfc)

[eslint-github-bot]

Hi @niteshseram!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @niteshseram!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[ljharb]

Suggested change

	- [ ] I have read the [contributing guidelines](https://github.com/eslint/eslint/blob/main/CONTRIBUTING.md).
	- [ ] I have read the [contributing guidelines](https://github.com/eslint/eslint/blob/HEAD/CONTRIBUTING.md).

this way it will always work, now and later, and won't need to be coordinated with the default branch change.

Same for every URL in the PR.

[niteshseram]

Thanks for the review @ljharb. I made the changes in all the URLs.

[nzakas]

Nice! Thanks for doing this. We will have to coordinate renaming the master branch with merging this PR.

[ljharb]

@nzakas the way it’s written, you don’t - you can merge this, and only the instructions will be wrong until you change the branch.

[nzakas]

@ljharb good point! I'll just wait for @mdjermanovic to ensure his concerns were addressed.

[mdjermanovic]

LGTM, thanks!

[mdjermanovic]

It seems that GitHub does not redirect edit/master links to edit/main links.

This is a link to update one document in eslint/espree (which was switched from master to main):

https://github.com/eslint/espree/edit/main/docs/tokens.md

But it doesn't redirect the same link with master:

https://github.com/eslint/espree/edit/master/docs/tokens.md

So, we'll have to update all edit links manually in eslint/website when we switch eslint/eslint to main. Otherwise, they will be broken until the final ESLint v8.0.0 release overwrites them.