Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,555,496
Community Members
 
Community Events
184
Community Groups

Display Changes to the Target Branch in PR

Mircea Marin
Mircea Marin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
Feb 15, 2018

Hi,

I was wondering if anyone knows of a way to highlight the fact that the source branch is out of date with the target branch, preferably on the PR screen. This would be something similar to the current information showing conflicts. Would be nice to also have the option block a merge if this happens.

A "workaround" would be to enforce "Fast-forward only" as the merge strategy but then changes to the target branch would be highlighted and addressed only when everything else is done and we're ready to merge which is too late.

Any ideas on how to achieve this?

Thanks!

Comment
Watch
Like Be the first to like this
537 views

0 comments

Comment

Log in or Sign up to comment
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events