chore: rename default branch to 'main' (typescript-eslint#4171)

Author: Josh Goldberg

.github/ISSUE_TEMPLATE.md

@@ -15,7 +15,7 @@ The more relevant information you can include, the faster we can find the issue
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/config.yml

@@ -3,8 +3,8 @@ contact_links:
   -
     name: FAQ
     about: Please check out our FAQ before filing new issues
-    url: https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md
+    url: https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md
   -
     name: Getting Started Guide
     about: If you're looking for help setting up check out our getting started guide
-    url: https://github.com/typescript-eslint/typescript-eslint/tree/master/docs/getting-started
+    url: https://github.com/typescript-eslint/typescript-eslint/tree/main/docs/getting-started

.github/ISSUE_TEMPLATE/documentation-request.md

@@ -14,7 +14,7 @@ The more relevant information you can include, the faster we can find the issue
 -->
 
 - [ ] I have looked on [typescript-eslint.io](https://typescript-eslint.io).
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/FAQ.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/FAQ.md) and my problem is not listed.
 
 ## Suggested Changes
 

.github/ISSUE_TEMPLATE/eslint-plugin-tslint.md

@@ -23,7 +23,7 @@ If you have a problem with a specific lint rule, please back out and select the
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/eslint-plugin-typescript.md

@@ -22,13 +22,13 @@ Are you opening an issue because the rule you're trying to use is not found?
 1) Check the releases log: https://github.com/typescript-eslint/typescript-eslint/releases
     -  If the rule isn't listed there, then chances are it hasn't been released to the main npm tag yet.
 2) Try installing the `canary` tag: `npm i @typescript-eslint/eslint-plugin@canary`.
-    - The canary tag is built for every commit to master, so it contains the bleeding edge build.
+    - The canary tag is built for every commit to main, so it contains the bleeding edge build.
 3) If ESLint still can't find the rule, then consider reporting an issue.
 -->
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/eslint-plugin-typescript.yml

@@ -11,7 +11,7 @@ body:
       value: |
         Before opening a new issue:
         - Look for existing [open or closed rule proposals](https://github.com/typescript-eslint/typescript-eslint/issues?q=label%3A%22enhancement%3A+new+base+rule+extension%22)
-        - Look for [existing rules](https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin)
+        - Look for [existing rules](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin)
         - Ensure that the rule you want to propose is related to types. If not, consider looking into [eslint-plugin-unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn)
   - type: textarea
     validations:

.github/ISSUE_TEMPLATE/typescript-eslint-parser.md

@@ -24,7 +24,7 @@ If you have a problem with a specific lint rule, please back out and select the
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/typescript-eslint-scope-manager.md

@@ -24,7 +24,7 @@ If you have a problem with the parser, please back out and select the `@typescri
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/typescript-eslint-utils.md

@@ -24,7 +24,7 @@ If you have a problem with the parser, please back out and select the `@typescri
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/ISSUE_TEMPLATE/typescript-estree.md

@@ -23,7 +23,7 @@ If you have a problem with a specific lint rule, please back out and select the
 
 - [ ] I have tried restarting my IDE and the issue persists.
 - [ ] I have updated to the latest version of the packages.
-- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
+- [ ] I have [read the FAQ](https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/getting-started/linting/TROUBLESHOOTING.md) and my problem is not listed.
 
 **Repro**
 

.github/pull_request_template.md

@@ -7,7 +7,7 @@ Please fill out all fields below -- otherwise we may not be able to review your
 
 -   [ ] Addresses an existing issue: fixes #000
 -   [ ] That issue was marked as [accepting prs](https://github.com/typescript-eslint/typescript-eslint/issues?q=is%3Aopen+is%3Aissue+label%3A%22accepting+prs%22)
--   [ ] Steps in [CONTRIBUTING.md](https://github.com/typescript-eslint/typescript-eslint/blob/master/CONTRIBUTING.md) were taken
+-   [ ] Steps in [CONTRIBUTING.md](https://github.com/typescript-eslint/typescript-eslint/blob/main/CONTRIBUTING.md) were taken
 
 ## Overview
 

.github/workflows/ci.yml

@@ -3,7 +3,7 @@ name: CI
 on:
   push:
     branches:
-      - master
+      - main
       - v5
   pull_request:
     branches:
@@ -310,7 +310,7 @@ jobs:
         linting_and_style,
         integration_tests,
       ]
-    if: github.repository == 'typescript-eslint/typescript-eslint' && github.ref == 'refs/heads/master'
+    if: github.repository == 'typescript-eslint/typescript-eslint' && github.ref == 'refs/heads/main'
     steps:
       - uses: actions/checkout@v2
       # Fetch all history for all tags and branches in this job because lerna needs it

CONTRIBUTING.md

@@ -24,7 +24,7 @@ Please refrain from leaving useless comments on issues. Comments like "+1", or "
 
 Please refrain from commenting on old, closed issues and PRs. Your issue is rarely related enough to a closed issue to warrant "necroing" a dead thread - raising a new issue means you can fill in the template, and make it easier for us to help you. Often times if you comment on a closed issue, we will just ask you to open a new issue, so please save everyone's time, and **_help us to help you_**.
 
-Please refrain from commenting on `master` commits. Commit comments are not searchable, meaning that nobody else can discover your comments. Raise an issue and reference the commit instead so that everyone can see your comment, and you can fill out the template.
+Please refrain from commenting on `main` commits. Commit comments are not searchable, meaning that nobody else can discover your comments. Raise an issue and reference the commit instead so that everyone can see your comment, and you can fill out the template.
 
 ---
 
@@ -88,7 +88,7 @@ Within the body of your PR, make sure you reference the issue that you have work
 
 Make sure you use the "Fixes #xxx" format to reference issues, so that GitHub automatically closes the issues when we merge the PR. Also note that if you are fixing multiple issues at once, you can only reference one issue per line, and must put one "Fixes #xxx" per issue number.
 
-In terms of your commit history - we do not care about the number, or style of commits in your history, because we squash merge every PR into master. Feel free to commit in whatever style you feel comfortable with.
+In terms of your commit history - we do not care about the number, or style of commits in your history, because we squash merge every PR into `main`. Feel free to commit in whatever style you feel comfortable with.
 
 **_One thing we ask is to please avoid force pushing after you have raised a PR_**. GitHub is not able to track changes across force pushes, which makes it impossible to efficiently do incremental reviews. This slows us down, and means it will take longer for us to get your PR merged.
 
@@ -98,4 +98,4 @@ With your PR raised, and the CI showing green, your PR will [sit in the queue to
 
 Please note that as this project is maintained by volunteers, it may take a while for us to get around to your PR (sometimes a month or more). Be patient, we'll get to it. Please refrain from commenting asking for a review, or similar bump comments. **_These just create spam for maintainers, and does not push your PR higher in the queue_**.
 
-Once we have reviewed your PR, we will provide any feedback that needs addressing. If you feel a requested change is wrong, don't be afraid to discuss with us in the comments. Once the feedback is addressed, and the PR is reviewed, we'll ensure the branch is up to date with master, and merge it for you.
+Once we have reviewed your PR, we will provide any feedback that needs addressing. If you feel a requested change is wrong, don't be afraid to discuss with us in the comments. Once the feedback is addressed, and the PR is reviewed, we'll ensure the branch is up to date with `main`, and merge it for you.

README.md

@@ -35,15 +35,15 @@ See https://typescript-eslint.io/docs/development/architecture/packages for more
 
 All of the packages are published with the same version number to make it easier to coordinate both releases and installations.
 
-We publish a canary release on every successful merge to master, so **you never need to wait for a new stable version to make use of any updates**.
+We publish a canary release on every successful merge to `main`, so **you never need to wait for a new stable version to make use of any updates**.
 
 Additionally, we promote the to the `latest` tag on NPM once per week, **on Mondays at 1 pm Eastern**.
 
 The latest version under the `latest` tag is:
 
 <a href="https://www.npmjs.com/package/@typescript-eslint/parser"><img src="https://img.shields.io/npm/v/@typescript-eslint/parser/latest.svg?style=flat-square" alt="NPM Version" /></a>
 
-The latest version under the `canary` tag **(latest commit to master)** is:
+The latest version under the `canary` tag **(latest commit to `main`)** is:
 
 <a href="https://www.npmjs.com/package/@typescript-eslint/parser"><img src="https://img.shields.io/npm/v/@typescript-eslint/parser/canary.svg?style=flat-square" alt="NPM Version" /></a>
 

docs/development/architecture/PACKAGES.md

@@ -69,10 +69,10 @@ Any custom rules you write generally will be as well.
 **TSLint is deprecated.** It is in your best interest to migrate off it entirely. See [Linting > TSLint](../../linting/TSLINT.md).
 :::
 
-[`@typescript-eslint/eslint-plugin-tslint`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin-tslint
-[`@typescript-eslint/eslint-plugin`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin
-[`@typescript-eslint/experimental-utils`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/experimental-utils
-[`@typescript-eslint/parser`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/parser
-[`@typescript-eslint/scope-manager`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/scope-manager
-[`@typescript-eslint/typescript-estree`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/typescript-estree
-[`@typescript-eslint/typescript-estree`]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/typescript-estree
+[`@typescript-eslint/eslint-plugin-tslint`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin-tslint
+[`@typescript-eslint/eslint-plugin`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin
+[`@typescript-eslint/experimental-utils`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/experimental-utils
+[`@typescript-eslint/parser`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/parser
+[`@typescript-eslint/scope-manager`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/scope-manager
+[`@typescript-eslint/typescript-estree`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/typescript-estree
+[`@typescript-eslint/typescript-estree`]: https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/typescript-estree

docs/linting/TSLINT.md

@@ -12,11 +12,11 @@ TSLint was a linter equivalent to ESLint that was written specifically to work d
 
 If you are looking for help in migrating from TSLint to ESLint, see [`tslint-to-eslint-config`](https://github.com/typescript-eslint/tslint-to-eslint-config).
 
-You can look at [`the plugin ROADMAP.md`](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/ROADMAP.md) for an up to date overview of how TSLint rules compare to the ones in this package.
+You can look at [`the plugin ROADMAP.md`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/ROADMAP.md) for an up to date overview of how TSLint rules compare to the ones in this package.
 
 There is also the ultimate fallback option of using both linters together for a while during your transition if you
 absolutely have to by using TSLint _within_ ESLint.
-For this option, check out [`@typescript-eslint/eslint-plugin-tslint`](https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin-tslint).
+For this option, check out [`@typescript-eslint/eslint-plugin-tslint`](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin-tslint).
 
 ## Why Deprecate TSLint?
 

nx.json

@@ -8,7 +8,7 @@
     ".github/workflows/ci.yml": "*"
   },
   "affected": {
-    "defaultBase": "master"
+    "defaultBase": "main"
   },
   "workspaceLayout": {
     "libsDir": "packages"