Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: enable GH actions when forking #244

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore: enable GH actions when forking #244

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ced81ba
chore: enable GH actions when forking
fty4 Oct 27, 2023
acecdbc
chore: use 1 as listing point
fty4 Oct 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 5 additions & 4 deletions CONTRIBUTORS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,8 @@ If e.g. environment parameters are changed, the action should be tested end-to-e
To do this, please follow this process:

1. Fork the repo.
2. Create a PR in **your own repo**.
3. The "Lint PR title preview (current branch)" workflow will run the new version and will help you validate the change.
4. Create a PR to this repo with the changes. In this case the preview workflow will fail, but we'll know that it works since you've tested it in the fork. Please include a include a link to a workflow where you've tested the current state of this pull request.
5. Don't run `npm run build` to update the `dist` folder as it will be generated on CI during the build
1. Enable GitHub Actions in your repository.
1. Create a PR in **your own repo**.
1. The "Lint PR title preview (current branch)" workflow will run the new version and will help you validate the change.
1. Create a PR to this repo with the changes. In this case the preview workflow will fail, but we'll know that it works since you've tested it in the fork. Please include a include a link to a workflow where you've tested the current state of this pull request.
1. Don't run `npm run build` to update the `dist` folder as it will be generated on CI during the build