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.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
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!
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.
Cutting a new branch from Jira interface automatically runs the default pipeline
Edited
Is there a way to get new branches that are cut at the server (rather than remotely) to NOT trigger the default pipeline? I know that one way would be to not have a `default` pipeline, and set up builds to only happen in the `pull-requests` section, but is there another way to get branches to only build upon pushing change to a branch, rather upon the fresh cut?
Seems wasteful to have a new branch automatically build, since it's a copy of master and is almost guaranteed to build successfully. Basically doubles our build minutes, per branch.
Looking back through the archives, it seems that this was a problem for Bamboo, too.
EDIT for clarification: by "cut from Jira interface," I mean going to the side nav of a ticket and clicking on the "Create a Branch" link:
