@stoplight/json-ref-resolver
Advanced tools
Comparing version 1.0.10 to 1.0.11
{ | ||
"name": "@stoplight/json-ref-resolver", | ||
"version": "1.0.10", | ||
"version": "1.0.11", | ||
"description": "Recursively resolve JSON pointers and remote authorities.", | ||
@@ -16,3 +16,4 @@ "keywords": [ | ||
"files": [ | ||
"**/*" | ||
"**/*", | ||
"!__tests__" | ||
], | ||
@@ -19,0 +20,0 @@ "author": "Stoplight <support@stoplight.io>", |
@@ -90,10 +90,10 @@ # JSON Ref Resolver | ||
1. Clone repo | ||
2. Create / checkout `feature/{name}`, `chore/{name}`, or `fix/{name}` branch | ||
3. Install deps: `yarn setup` | ||
4. Make your changes | ||
5. Run tests: `yarn test.prod` | ||
6. Stage relevant files to git | ||
1. Clone repo. | ||
2. Create / checkout `feature/{name}`, `chore/{name}`, or `fix/{name}` branch. | ||
3. Install deps: `yarn`. | ||
4. Make your changes. | ||
5. Run tests: `yarn test.prod`. | ||
6. Stage relevant files to git. | ||
7. Commit: `yarn commit`. _NOTE: Commits that don't follow the [conventional](https://github.com/marionebl/commitlint/tree/master/%40commitlint/config-conventional) format will be rejected. `yarn commit` creates this format for you, or you can put it together manually and then do a regular `git commit`._ | ||
8. Push: `git push` | ||
9. Open PR targeting the `develop` branch | ||
8. Push: `git push`. | ||
9. Open PR targeting the `develop` branch. |
72775