master ➡️ main

Author: curtisblackwell

.github/pull_request_template.md

@@ -28,4 +28,4 @@
 
 
 
-[directory-structure]: ../tree/master/standards#directory-structure
+[directory-structure]: ../tree/main/standards#directory-structure

standards/README.md

@@ -18,23 +18,23 @@ Proposals must include:
 ### Proposal
 #### New standard
 1. Check that no one else has begun working on the same proposal by checking open branches and/or asking the other devs.
-2. Branch off of `master`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `proposal-` (e.g. `proposal-practices-linting`).
+2. Branch off of `main`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `proposal-` (e.g. `proposal-practices-linting`).
 3. Push the empty branch immediately for visibility and to help prevent duplicate efforts.
 4. Draft your proposal using the [standard template](../template-standard.md).
 5. Create a pull request with a descriptive title.
 6. Find another developer to perform the first, cursory review.
 
 #### Amendment
 1. Check that no one else has begun working on the same amendment by checking open branches and/or asking the other devs.
-2. Branch off of `master`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `amendment-` (e.g. `amendment-practices-linting`).
+2. Branch off of `main`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `amendment-` (e.g. `amendment-practices-linting`).
 3. Push the empty branch immediately for visibility and to help prevent duplicate efforts.
 4. Draft your changes.
 5. Create a pull request with a descriptive title.
 6. Find another developer to perform the first, cursory review.
 
 #### Repeal
 1. Check that no one else has begun working on the same repeal by checking open branches and/or asking the other devs.
-2. Branch off of `master`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `repeal-` (e.g. `repeal-practices-linting`).
+2. Branch off of `main`. Name the branch after the [filepath](#directory-structure) using kebab-case, prefixed with `repeal-` (e.g. `repeal-practices-linting`).
 3. Push the empty branch immediately for visibility and to help prevent duplicate efforts.
 4. Draft your changes.
 5. Create a pull request with a descriptive title and informative comment.

standards/practices/linting.md

@@ -26,7 +26,7 @@ Run from project root:
 
 ```sh
 npm i -D eslint @highlandsolutions/eslint-config-highland
-curl https://raw.githubusercontent.com/HighlandSolutions/development-standards/master/assets/linting/.eslintrc.js > .eslintrc.js
+curl https://raw.githubusercontent.com/HighlandSolutions/development-standards/main/assets/linting/.eslintrc.js > .eslintrc.js
 ```
 
 Tweak `.eslintrc.js` as needed. For example, you might need to enable linting for Vue, add a global, or tweak import resolution.
@@ -51,5 +51,5 @@ Run from project root:
 
 ```sh
 composer require --dev friendsofphp/php-cs-fixer
-curl https://raw.githubusercontent.com/HighlandSolutions/development-standards/master/assets/linting/.php_cs > .php_cs
+curl https://raw.githubusercontent.com/HighlandSolutions/development-standards/main/assets/linting/.php_cs > .php_cs
 ```