Replace as many references to master with main as currently possible (#561)

Author: Andarist

.changeset/README.md

@@ -2,4 +2,4 @@
 
 Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with mono-repos or single package repos to help you version and release your code. You can find the full documentation for it [in our repository](https://github.com/changesets/changesets)
 
-We have a quick list of common questions to get you started engaging with this project in [our documentation](https://github.com/changesets/changesets/blob/master/docs/common-questions.md)
+We have a quick list of common questions to get you started engaging with this project in [our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.circleci/config.yml

@@ -15,7 +15,10 @@ jobs:
  name: Install
  command: yarn install --pure-lockfile
  - run:
- name: GitSetup
+ name: Check Git version
+ command: git --version
+ - run:
+ name: "Git Setup"
  command: git config --global user.email "you@example.com" && git config --global user.name "Your Name"
  - run:
  name: "Jest Tests"

.github/workflows/changeset-version.yml

@@ -3,7 +3,7 @@ name: Release
 on:
  push:
  branches:
- - master
+ - main
 
 jobs:
  release:

docs/adding-a-changeset.md

@@ -68,4 +68,4 @@ Changesets are designed to stack, so there's no problem with adding multiple. Yo
 
 ## I want to know more about changesets
 
-[here is a more in-depth explanation](https://github.com/Noviny/changesets/blob/master/docs/detailed-explanation.md)
+[here is a more in-depth explanation](https://github.com/atlassian/changesets/blob/main/docs/detailed-explanation.md)

docs/automating-changesets.md

@@ -41,15 +41,15 @@ In some cases, you may _want_ to merge a change without doing any releases (such
 We have a [github action](https://github.com/changesets/action) that
 
 - creates a `version` PR, then keeps it up to date, recreating it when merged. This PR always has an up-to-date run of `changeset version`
-- Optionally allows you to do releases when changes are merged to master.
+- Optionally allows you to do releases when changes are merged to the base branch.
 
 If you don't want to use this action, the manual workflow we recommend for running the `version` and `publish` commands is:
 
-- A release coordinator (RC) calls to stop any merging to master
-- The RC pull down `master`, runs `changeset version`, then make a new PR with the versioning changes
-- The versioning changes are merged back into master
-- The RC pulls `master` again and runs `changeset publish`
+- A release coordinator (RC) calls to stop any merging to the base branch
+- The RC pull down the base branch, runs `changeset version`, then make a new PR with the versioning changes
+- The versioning changes are merged back into the base branch
+- The RC pulls the base branch again and runs `changeset publish`
 - The RC runs `git push --follow-tags` to push the release tags back
-- The RC unblocks merging to master
+- The RC unblocks merging to the base branch
 
-This is a lot of steps, and is quite finnicky (we have to pull from master twice). Feel free to finesse it to your own circumstances.
+This is a lot of steps, and is quite finnicky (we have to pull from the base branch twice). Feel free to finesse it to your own circumstances.

docs/command-line-options.md

@@ -73,7 +73,7 @@ changeset version
 
 This is one of two commands responsible for releasing packages. The version command takes changesets that have been made and updates versions and dependencies of packages, as well as writing changelogs. It is responsible for all file changes to versions before publishing to npm occurs.
 
-> We recommend making sure changes made from this commmand are merged back into master before you run publish.
+> We recommend making sure changes made from this commmand are merged back into the base branch before you run publish.
 
 Version has two options, `ignore` and `snapshot`:
 

docs/decisions.md

@@ -57,4 +57,4 @@ This decision is open for discussion.
 
 ## How Changesets interacts with Git
 
-Changesets core flow of adding changesets, versioning packages/writing changelogs and publishing packages should work without Git. Using Git in a way where the user doesn't explicitly ask to do something that involves Git such as showing changed packages in the add command shouldn't show an error if Git fails for any reason. Using Git in a way where the user explicitly chooses to use Git such as using the commit option or `status --since-master`, Changesets should log an error and fail with a non-zero exit code.
+Changesets core flow of adding changesets, versioning packages/writing changelogs and publishing packages should work without Git. Using Git in a way where the user doesn't explicitly ask to do something that involves Git such as showing changed packages in the add command shouldn't show an error if Git fails for any reason. Using Git in a way where the user explicitly chooses to use Git such as using the commit option or `status --since main`, Changesets should log an error and fail with a non-zero exit code.

docs/prereleases.md

@@ -34,7 +34,7 @@ packages/
 yarn changeset pre enter next
 ```
 
-This command changes Changesets into prerelease mode which creates a `pre.json` file in the `.changeset` directory which stores information about the state the prerelease is in. For the specific data stored in the `pre.json` file, see the type definition of `PreState` in [`@changesets/types`](https://github.com/atlassian/changesets/tree/master/packages/types).
+This command changes Changesets into prerelease mode which creates a `pre.json` file in the `.changeset` directory which stores information about the state the prerelease is in. For the specific data stored in the `pre.json` file, see the type definition of `PreState` in [`@changesets/types`](https://github.com/atlassian/changesets/tree/main/packages/types).
 
 ```
 yarn changeset version

packages/apply-release-plan/CHANGELOG.md

@@ -204,7 +204,7 @@
 
 ### Minor Changes
 
-- [`8f0a1ef`](https://github.com/atlassian/changesets/commit/8f0a1ef327563512f471677ef0ca99d30da009c0) [#183](https://github.com/atlassian/changesets/pull/183) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Add support for prereleases. For more information, see [the docs on prereleases](https://github.com/atlassian/changesets/blob/master/docs/prereleases.md).
+- [`8f0a1ef`](https://github.com/atlassian/changesets/commit/8f0a1ef327563512f471677ef0ca99d30da009c0) [#183](https://github.com/atlassian/changesets/pull/183) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Add support for prereleases. For more information, see [the docs on prereleases](https://github.com/atlassian/changesets/blob/main/docs/prereleases.md).
 
 ### Patch Changes
 

packages/apply-release-plan/package.json

@@ -5,7 +5,7 @@
  "main": "dist/apply-release-plan.cjs.js",
  "module": "dist/apply-release-plan.esm.js",
  "license": "MIT",
- "repository": "https://github.com/changesets/changesets/tree/master/packages/apply-release-plan",
+ "repository": "https://github.com/changesets/changesets/tree/main/packages/apply-release-plan",
  "dependencies": {
  "@babel/runtime": "^7.10.4",
  "@changesets/config": "^1.5.0",