-
Notifications
You must be signed in to change notification settings - Fork 219
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
Allow to configure the branch where the pull request is created #88
Comments
Hm, the git-flow is quite popular so I'm inclined to say that maybe we should provide better means to deal with this in the core. It should be possible to add a step that would just change the base of created PR. Which we could make even easier if we'd output the PR number. The downside of this approach though is that it would mess up this search: Line 206 in c291823
As to the more built-in support for this - any ideas regarding the API, config option names etc? |
I think my first idea (which might be wrong) is to have just a |
Hm, it could be still confusing to have those two in the config - although I agree that the chosen name has a nice ring to it. The problem is not really in that proposed flag, but more in the existing That option would also only be relevant for the action here (at least for now) which kinda adds to the confusion. OTOH - the CLI (and its config) is a central place and people don't care that much how our architecture is fragmented right now in the CLI, Action, and Bot. So this could be thought of as a DX improvement. @mitchellhamilton any particular thoughts about this? |
Having a target branch option (in the action config, not the changesets config) seems fine. |
Hi all, any decisions made on this issue? |
I would also like to know if there's any progress on this? |
Hi, I would like to know if you are open to the idea of having the ability to change the branch that the release pull request is created via an option.
For the context, in my company we are using the git-flow process, all the code changes are merged into our
develop
branch, we create a release branch targetingmaster
with all the changes and then once merged, merge master into our develop branch.We would like to start using changeset into our flow but with this action the new release pr is always targeting our
develop
branch but we would like it to point tomaster
.I hope my use case is clear, if you think this change makes sense I can work on this :)
The text was updated successfully, but these errors were encountered: