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

This is a large pull request. Large pull requests can only be viewed by loading files individually.

Getting this message for "large Pull Requests". Instead of scrolling through the files they then need to be opened one-by-one. 

When is a PR considered "large"?

Why can we not disable that behavior?


Curious to know the answer as well.

i think it's considered large on 99+ files ... and when it;s most needed you need to click on each file !!! we have aggregated PR so in the start most part of PR is reviewed when it reaches the limit, it can be only one file change but I don't know which and I must look in every single file one by one that is unusable ... 

Certain types of resources can be quite large, requiring excessive processing on Bitbucket Cloud. Because of this, limits are set to ensure requests complete in a reasonable amount of time.

i can wait a minute instead of clicking 100 times !!

by the way here   limits are described

I think this is egregious.  I see a benefit for being forced to organize code into separate repos when it becomes large, but we're trying to push as much code as possible and this is a real drag to suddenly have to scroll through all the files..

Like # people like this

Please make this configurable or increase the size.

A namespace refactor can touch 100s of files which are easily eyeballed when on one screen.

File by file just creates cba PRs tbf.

Like Ion Mihov likes this

It must be optional or it's useless.

Like Ion Mihov likes this

So wait a minute... 

Bitbucket has no problem showing YOU the creator of PR the whole diff without hesitation

BUT somehow showing it once it's ON is "bad"

As others have mentioned you must go through it 1 by 1 when for example some change spans over 200 files but it's just a namespace change and you can just scroll through it all without a problem.

This is ridiculous

Like # people like this

This is ridiculous!

I can see there is an option that keep old diff UI with extendable panel for each file. 

Sergei Benkovich
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 06, 2023

any resolution yet...? still very frustrating, even a scroll down of all the files would be useful 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events