You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ci: manually trigger publishing in release.yml
* refactor: replace yarn with npm
* ci: fix npm publish command
* Revert "ci: manually trigger publishing in release.yml"
This reverts commit 9ddef07.
* ci: temporarly add publish step in test workflow
* build: apply suggested npm fix to package.json
* ci: reset test workflow to original
* ci: temporarly trigger release.yml workflow on pull requests
* chore: bump & enforce npm version
* chore: add packageManager field in pacakge.json
* ci: factor setting up the repo in a common composite action
* ci: remove checkout from common setup
* ci: fix call to custom composite setup
* ci: manually install npm in setup
* ci: restore original release workflow
Copy file name to clipboardExpand all lines: .devcontainer/devcontainer.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@
20
20
// "forwardPorts": [],
21
21
22
22
// Use 'postCreateCommand' to run commands after the container is created.
23
-
"postCreateCommand": "yarn install",
23
+
"postCreateCommand": "npm install",
24
24
25
25
// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
@@ -12,16 +12,16 @@ Please note that this project is released with a [Contributor Code of Conduct][c
12
12
## Submitting a pull request
13
13
14
14
1.[Fork][fork] and clone the repository
15
-
1. Configure and install the dependencies: `yarn install`
16
-
1. Make sure the tests pass on your machine: `yarn test`, note: these tests also apply the linter, so no need to lint separately
17
-
1. Create a new branch: `git checkout -b my-branch-name`
18
-
1. Make your change, add tests, build with `yarn prettier && yarn lint --fix && yarn build` and make sure the tests still pass
19
-
1. Push to your fork and [submit a pull request][pr]
20
-
1. Give yourself a high five, and wait for your pull request to be reviewed and merged.
15
+
2. Configure and install the dependencies: `npm install`
16
+
3. Make sure the tests pass on your machine: `npm run test`, note: these tests also apply the linter, so no need to lint separately
17
+
4. Create a new branch: `git checkout -b my-branch-name`
18
+
5. Make your change, add tests, build with `npm run prettier && npm run lint --fix && npm run build` and make sure the tests still pass
19
+
6. Push to your fork and [submit a pull request][pr]
20
+
7. Give yourself a high five, and wait for your pull request to be reviewed and merged.
21
21
22
22
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
23
23
24
-
- Follow the [style guide][style] which is using standard. Any linting errors should be shown when running `yarn test`
24
+
- Follow the [style guide][style] which is using standard. Any linting errors should be shown when running `npm run test`
25
25
- Write and update tests.
26
26
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
27
27
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
0 commit comments