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
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.