feat(git): allow commit-and-push to different target branch #19680
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
6 tasks
viceice
reviewed
Jan 5, 2023
viceice
changed the title
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
viceice
reviewed
Jan 5, 2023
- (default)commitFiles function should push to same branch name - config-migration: use config.defaultBranch instead of config.baseBranch as targetBranch parameter
viceice
reviewed
Jan 14, 2023
# Conflicts: # lib/workers/repository/config-migration/branch/rebase.spec.ts
viceice
approved these changes
Jan 23, 2023
|
Needs to be updated from main branch before it can merge |
|
🎉 This PR is included in version 34.112.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
allow (optionally) to push to different target branch, target defaults to source branch name.
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: