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,463,409
Community Members
 
Community Events
176
Community Groups

"pull-requests" syntax question

The Configure bitbucket-pipelines.yml doc shows the syntax for pull-request pipelines as such:

pipelines:
pull-requests:
'**': #this runs as default for any branch not elsewhere defined
- step:
script:
- ...
feature/*: #any branch with a feature prefix
- step:
script:
- ...

Do the entries in the pull-requests section represent the source branch, or the destination branch?

That is to say, if I want to merge `branch1` into `master`, would my pull-request entry say `branch1`, or `master`?

1 answer

1 accepted

0 votes
Answer accepted

@inger_klekacz The entry represents the source branch. As per your example, it would be `branch`. I will raise an internal ticket to update the docs, thanks for the feedback.

...`branch1`, you mean, right? not `branch`? Thanks for getting back to me!

@Justin Thomas So how can I match the destination branch if I want to do some trigger with PR to destination branch?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events