Add GitHub Actions workflow to create merge-up pull requests #1248
Conversation
This file contains 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
alcaeus
commented
Mar 7, 2024
| with: | ||
| ref: ${{ github.ref_name }} | ||
| branchNamePattern: 'v<major>.<minor>' | ||
| fallbackBranch: 'master' |
There was a problem hiding this comment.
This ensures that if no newer versioned branch name is found, a pull request to master is created. The list of branches checked when pushing to v1.17 would thus be:
- v1.18
- v2.0
- master
There was a problem hiding this comment.
Noted that this is the only difference from mongodb/laravel-mongodb#2748
jmikola
approved these changes
Mar 7, 2024
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.
Similar to the corresponding change in laravel-mongodb, this new workflow ensures that changes pushed to older branches are merged up to newer branches.