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,455,327
Community Members
 
Community Events
175
Community Groups

In Build Setup happens git merge with destination branch head - How I disable it?

Bitbucket Pipelines

When a Pipeline was trigger, the Build Setup merges with destination branch head. PyLint broke in this case, as it checks something out of what has been modified, so how do I disable it?

Screenshot(2).png

1 answer

1 accepted

0 votes
Answer accepted
Patrik S Atlassian Team Jan 25, 2023

Hello @Rodolfo dos Santos ,

Welcome to Atlassian Community!

The merge is happening because you are most likely using a Pull request triggered pipeline.

Pull request triggered pipelines behave a little differently than other types of pipelines, as it merges the destination branch into your working branch during the Build Setup. This is the intended behavior, as when you run a pull request pipeline you are usually interested to know if merging the content from the source and destination branches will break your build.

In case you do not want the merge to happen, you will need to use a different type of pipelines, such as branch pipelines. Branch pipelines will be triggered every time a new commit is pushed to a given branch or branch pattern you have configured, as in the below example : 

image: node:lts
pipelines:
  default:
    - step:
        script:
          - echo "This script runs on all branches that don't have any specific pipeline assigned in 'branches'."
  branches:
    main:
      - step:
          script:
            - echo "This script runs only on commit to the main branch."
    feature/*:
      - step:
          image: openjdk:8 # This step uses its own image
          script:
            - echo "This script runs only on commit to branches with names that match the feature/* pattern."

Branches pipelines will run for a specific commit, and will not be merged to any other commit.

For more details on what types of pipeline triggers can be configured, you can refer to Pipelines start conditions.

Hope that helps!  Let me know in case you have any questions.

Thank you, @Rodolfo dos Santos .

Patrik S

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events