ci: semver-check action doesn't run on PRs from same repo
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 288
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
While testing a CI change I noticed that the pull_request_target trigger means that branches pushed to this fork, will not trigger pull_request_target PR checks, hence the semver labels can't be applied.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's GitHub Actions workflow that runs the semver-check action and review how its pull request trigger handles branches from the same repository. Confirm the behavior with a same-repository pull request; done when the semver check runs and applies the expected labels there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100