CI: do not use pr.yml workflow name for verifying main branch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
The repo is setup in such a way that both main branch and PR verifications run pr.yml workflow in GitHub actions.
As a team we track build failures in #builds slack channel, and we want to distinguish failing CI on PRs from failing CI on main, so we ignore PRs but get alerted on main failures. Currently pr.yml is in the exclusion list so we do not get notified by either.
Desired change: dedicated workflow name for verifying main branch.
Affected area/feature
Contributor guide
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
Start by locating the pr.yml GitHub Actions workflow and inspect how it is used for both pull requests and the main branch. Separate the main-branch verification under a dedicated workflow name, then verify that pull request and main-branch failures can be distinguished for build notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100