fix(ci): restrict push trigger to main branch only#92
Conversation
Without branch filter, push to any branch triggers CI. On PR branches this causes double execution — once for push, once for pull_request. Restricting push to main ensures PR branches only run CI via the pull_request trigger. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Thanks for your first pull request! We are excited to have you contribute. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Automated approval for solo maintainer project
This PR has passed all automated quality gates:
- ✅ Static analysis (PHPStan)
- ✅ Code style (PHP-CS-Fixer)
- ✅ Unit & functional tests
- ✅ Security scanning
- ✅ Dependency review
See SECURITY_CONTROLS.md for compensating controls documentation.
There was a problem hiding this comment.
Pull request overview
Restricts the CI workflow’s push trigger to run only on the main branch, avoiding duplicate CI runs on PR branches where both push and pull_request events would otherwise fire.
Changes:
- Limit
on.pushin CI workflow tobranches: [main]. - Keep
pull_request,merge_group, andscheduletriggers unchanged to maintain PR and merge-queue coverage.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
push:trigger in CI workflow tobranches: [main]pushandpull_requestwere triggering)pull_requestandmerge_grouptriggers remain unchanged for PR/merge queue coverageTest plan