Repository navigation
Issue/627 Run the CI workflow for the maintenance branches - #628
Merged
armanist merged 1 commit intoOct 27, 2026
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #627.
What changed
.github/workflows/php.yml: the triggers are nowpull_requesthas nobranchesfilter, so a pull request into any branch runs the workflow, andpushruns formasterand for any branch whose name ends in.x, such as3.1.xand a later3.2.x, without another edit.Nothing else in the workflow changes: the PHP matrix, the services, the style, analysis and test steps, and the coverage upload.
Why
The workflow listed
branches: ["master"]under bothpushandpull_request, so a pull request into the maintenance branch3.1.xran no checks, and neither did a push to it. Laravel and Symfony keep the triggers open the same way (pushon a branch pattern,pull_request:with no filter).A merged pull request is a push to its target branch, so CI also runs on the merged result, as it does on
mastertoday.Breaking changes
None.
Testing
There is no PHP test for a workflow file. The file parses as valid YAML with the same single job, the
pull_requesttrigger has nobranchesfilter, and the*.xpattern, read with GitHub's rule that*does not match/, matches3.1.x,3.2.xand3.10.xbut notmaster,3.1.0,3.1or a ticket branch such asissue/627-ci-branch-triggers.Notes for reviewers
3.1.xand gets no CI itself: a pull request runs the workflow file of its base branch, and3.1.xstill has the old filter. The first run is the push after the merge.masterneeds the same change. It arrives when3.1.xis merged intomaster.