Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,093
Community Members
 
Community Events
184
Community Groups

Automatic Plan Branch creation for both pull requests and feature branches

Is it possible to automatically create plan branches on both a new pull request and a new feature branch creation? 

Environment: Git / Bitbucket, Bamboo, Maven

1 answer

0 votes
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 14, 2017

No, rationale behind this decision was "if you already have plan branch when new branch created in Git, why do you need another plan branch when PR created?"

If the Pull Request was created from a Fork, then a branch plan won't have already been created.

Noel is absolutely correct here. If you use a fork-based contribution model for your team (no branches allowed on central repo), then you do not get builds and feedback from those builds until the PR is created. Much earlier on, you want to push commits to your fork and get build feedback prior to creating your pull request.

I think Bamboo should be trained to monitor new branches on all forks of a central repository and create new branches based on activity on the fork, rather than pull request events which occur near the end of the lifecycle of a feature or bugfix. This will allow better continuous delivery.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events