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

Pipeline missed by some direct commits


Recently I noticed some strange behavior from the bitbucket pipeline, where the pipeline was missed by some direct commits and after a PR merge it again started working fine like earlier. The important thing to notice is the pipeline didn't fail nor gave any other error but it's completely missed for the same brnach i.e., master. I am sharing the screenshots for more details 


missing pipelines.png

1 answer

Good Day,

Could have this been a pull from origin master to local branch before push commit form local flow process followed.
I will assume if more than one is working on repo ,a branch off will be a more fervoured route.

Trust solution in route.

@Mathew Munava Thanks for the response, I am trying to find out that. Will confirm the you here. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events