Skip to content

Commit 4b2976d

Browse files
authored
chore: Format codebase with prettier (#955)
1 parent 13efbb3 commit 4b2976d

11 files changed

+397
-388
lines changed

.github/ISSUE_TEMPLATE.md

+1
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ supported version.
3131
Relevant code or config
3232

3333
```js
34+
3435
```
3536

3637
What you did:

.github/workflows/validate.yml

+4
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,10 @@ jobs:
3838
with:
3939
useLockFile: false
4040

41+
# TODO: Can be removed if https://github.com/kentcdodds/kcd-scripts/pull/146 is released
42+
- name: Verify format (`npm run format` committed?)
43+
run: npm run format -- --check --no-write
44+
4145
- name: ▶️ Run validate script
4246
run: npm run validate
4347

CONTRIBUTING.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ series [How to Contribute to an Open Source Project on GitHub][egghead]
1111
2. Run `npm run setup` to install dependencies and run validation
1212
3. Create a branch for your PR with `git checkout -b pr/your-branch-name`
1313

14-
> Tip: Keep your `main` branch pointing at the original repository and make
15-
> pull requests from branches on your fork. To do this, run:
14+
> Tip: Keep your `main` branch pointing at the original repository and make pull
15+
> requests from branches on your fork. To do this, run:
1616
>
1717
> ```
1818
> git remote add upstream https://github.com/testing-library/dom-testing-library.git
@@ -21,10 +21,10 @@ series [How to Contribute to an Open Source Project on GitHub][egghead]
2121
> ```
2222
>
2323
> This will add the original repository as a "remote" called "upstream," Then
24-
> fetch the git information from that remote, then set your local `main`
25-
> branch to use the upstream main branch whenever you run `git pull`. Then you
26-
> can make all of your pull request branches based on this `main` branch.
27-
> Whenever you want to update your version of `main`, do a regular `git pull`.
24+
> fetch the git information from that remote, then set your local `main` branch
25+
> to use the upstream main branch whenever you run `git pull`. Then you can make
26+
> all of your pull request branches based on this `main` branch. Whenever you
27+
> want to update your version of `main`, do a regular `git pull`.
2828
2929
## Committing and Pushing changes
3030

package.json

+1
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@
2525
},
2626
"scripts": {
2727
"build": "kcd-scripts build --no-ts-defs --ignore \"**/__tests__/**,**/__node_tests__/**,**/__mocks__/**\" && kcd-scripts build --no-ts-defs --bundle --no-clean",
28+
"format": "kcd-scripts format",
2829
"lint": "kcd-scripts lint",
2930
"setup": "npm install && npm run validate -s",
3031
"test": "kcd-scripts test",

0 commit comments

Comments
 (0)