The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Is there to automatically create a new branch with a PR?
Let's say there is a repo X in a project PROJ. This repo has a branch called release/1-0-0-0. The numbers represent a certain versioning format.
A DEV forks the repo into their personal. The DEV makes several changes and creates a new branch in DEV/A called release/1-0-1-0. Satisfied, the DEV creates PR from DEV/A to PROJ/A.
There are two ways of doing things. Either a new branch in PROJ/A is created and DEV creates the PR to that branch. Or, the PR is done towards release/1-0-0-0 branc, and before the PR is approved, a new branch is created and the merge happens with that one.
The first is un-desirable as if the PR is denied, the branch has to be deleted. The second is un-desirable as it is prone to human error. Ideally DEV should be able to specify that a new branch ought to be created when his PR is to be merged.
Is there any methods for doing this? If there are none, can this feature be implemeted?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.