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

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


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Run pipeline on merge

Deleted user Feb 02, 2018

Hi I'm currently having some trouble setting up a pipeline when I'm merging a feature branche in my develop branch and generating a Changelog.

Current situation

  • Pipeline is being triggerd on every push to develop.

Wished situation

  1. Trigger pipeline only when I merge a feature branch to develop.
  2. Generate changelog
  3. Push generated changelog to develop
  4. Don't run pipeline

Right now my pipeline is being stuck in a loop since I'm pushing my generate changelog to develop after the merge.


Current bitbucket-pipelines.yml

- step:
- node
script: # Modify the commands below to build your repository
- git config ""
- git config "my_name"
- npm install
- npm run release
- git push --follow-tags origin develop

 I hope you guys can help me out!

5 answers

This feature is yet to be implemented by atlassian dev team. I have added reasons why this feature would be ideal in two (of many more) scenarios to the aforementioned feature request:

Pramod I'm New Here Nov 30, 2022

Is this resolved?

any update on this ?

1 vote
SebC Atlassian Team Feb 06, 2018

Hey @[deleted], 

There's a feature request open at that I would love to get your feedback on.

We use bitbucket site/master issues to track customer requests and feedback on improvements we can make to Pipelines.



Was there an update on this issue?  

I was asked to execute a task upon a merge into master, and not on a master branch build.

Thank you.

0 votes

For future reference, you can disable triggering the pipeline by committing with "[skip ci]" in the commit message - see FAQ about this.
What I would do in the requested scenario is to actually implement CHANGELOG in the PR itself to be able to review it *before* merging to develop happens.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events