cypress-example-kitchensink
cypress-example-kitchensink copied to clipboard
Published
20 hours ago •
cypress-io
cypress-io
GHA admin workflows fail in fork on pull_request event
Issue
Two workflows for GitHub Actions triggered by pull_request events cause issues in a fork for pull requests with fork targets.
The workflows are:
| Workflow file | Workflow name | Failure reason |
|---|---|---|
| .github/workflows/add-issue-to-triage-board.yml | Add issue/PR to Triage Board | Secret ADD_TO_TRIAGE_BOARD_TOKEN missing |
| .github/workflows/semantic-pull-request.yml | Semantic Pull Request | Missing semantic prefix |
- The triage workflow is designed to manage pull requests targeting the main repo. PRs which involve only a fork should be out of scope for this workflow.
- The Semantic Pull Request workflow is to check commits flowing into the main repo's default branch. It does not fit the use case where a PR is created in a fork and the PR is not targeting the main repo at all. There is no need here for a PR to conform to semantic commit conventions.
Workarounds
Workaround - Disable workflows
Refer to the GitHub documentation Disabling and enabling a workflow, individually disable each of the workflows:
| Workflow name |
|---|
| Add issue/PR to Triage Board |
| Semantic Pull Request |
A third workflow, associated with issue_comment events might also be disabled at the same time:
| Workflow name |
|---|
| Handle Comment Workflow |
Related issues
- https://github.com/cypress-io/cypress-documentation/issues/5754
