George Berkshire
524e936cd9
Check dist / check-dist (push) Failing after 1s
CodeQL / Analyze (javascript) (push) Failing after 1s
Licensed / Check licenses (push) Failing after 0s
Build and Test / build (push) Failing after 1s
Build and Test / test (ubuntu-latest) (push) Failing after 1s
Build and Test / test-bypass-proxy (push) Failing after 2s
Build and Test / test-proxy (push) Failing after 22m37s
Build and Test / test (macos-latest) (push) Canceled after 0s
Build and Test / test (windows-latest) (push) Canceled after 0s
Build and Test / test-output (push) Canceled after 0s
Build and Test / test-git-container (push) Canceled after 1h13m23s
1.3 KiB
1.3 KiB
Contributing
Submitting a pull request
- Fork and clone the repository
- Configure and install the dependencies:
npm install - Create a new branch:
git checkout -b my-branch-name - Make your change, add tests, and make sure the tests still pass:
npm run test - Make sure your code is correctly formatted:
npm run format - Update
dist/index.jsusingnpm run build. This creates a single javascript file that is used as an entrypoint for the action - Push to your fork and submit a pull request
- Pat yourself on the back and wait for your pull request to be reviewed and merged
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
- Write tests.
- 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.
Resources
Thanks! ❤️ ❤️ ❤️
GitHub Actions Team :octocat: