Open cmitzel-ncino opened 1 year ago
taylor-sutton
commented
1 year ago Hi, am I understanding correctly that you would like to specify which branch is checked out when using microplane clone to then be used as the base of the change? Or are you suggesting that when the PR is created, specifying which branch the PR is attempting to merge into? (Or both? Or something else?)
from-nibly
commented
1 year ago For me both would be great. Cloning a specific branch, and then choosing which branch to merge into would be ideal.
We have a git flow like workflow that means checking out from non default branch, and possibly merging to non default branch.
cmitzel-ncino
commented
1 year ago Hey, sorry for the late response!
Both would also be great, but the main use case for use would be
1) Initialize/Clone a branch other than main (e.g. beta)
2) run microplane as usual
3) open a PR to merge it into the head/cloned branch (beta)
4) Merge if qualifications are met
Hey y'all, my company has been using microplane with great success over the past couple of years and it's an amazing tool. However, due to business realities, the tool doesn't cover all of our use cases - while keeping the main branch up to date is awesome, we have a number of
patchandbetabranches that cannot have the main branch merged but also need to be maintained. The tool's current limitations mean that we have to go in an manually make changes to 20-30 branches manually which is less than ideal for changes that could be automated. Is it possible to modify the tool such that you can specify a branch, either in a flag or the text file (e.g.org/repo@branch)?Thanks!