-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create MR with a custom target branch #69
Comments
It seems different with the original GitHub Action? Maybe it's worth to discuss this at https://github.com/changesets/action first? |
Thanks, then PR welcome to see how simple the change is. |
Is there any documentation on how to develop and test on this project? Even tho it seems to be an easy change to implement, I'd really like to test any changes before opening a PR |
Sorry, but no document yet. You can just raise the PR, then a codesandbox CI installation usage like #66 (comment) would be available to test on your own repository. |
Okay. I'll see if I can opena PR today. Regarding the implementation, it makes sense to want to use the |
A new env |
Right now, the MR is created with the target branch being the same as the one that's running the CI.
In our case, we use a branch
dev
for development and we'd like to merge all changes intomain
using the MR that changeset created. Problem is as I said, the target branch is alwaysdev
as it's usingCI_COMMIT_REF_NAME
. Could an option be added to specify a custom target branch? (Similar to how changeset has abaseBranch
configuration option for comparisons)As this is a quite simple change, I'd be uo tp opening a PR with such changes, maybe with a new
INPUT_TARGET_BRANCH
env variable?The text was updated successfully, but these errors were encountered: