Why I'm getting below information while reviewing the code, since I'm having only few changes in the code
"Now that is a lot of code! There's simply too much in this diff for us to render it all."
Hi @gowthamece,
While investigating this further I came across two improvement requests that relate to this message you're seeing:
Improve performance of large code reviews (BB-7555)
Friendlier web UI message for large commits (BB-15156)
Feel free to vote on these improvements and watch them.
While they are not available, as a workaround you can split the number of changes into smaller chunks so that others can view the PR in the UI before merging or review the changes locally, merge the PR and then push to Bitbucket.
Cheers,
Felipe
Thanks @Felipe Kraemer, hope we will get this feature (BB-7555) ASAP, because we are from VSTS to Bit Bucket
@Felipe Kraemer do you have any idea on when we will get these updates ?
The official response from Bitbucket staff on the feature BB-7555, in 2018-03-07, was:
Howdy! thanks for your continued interest in this ticket. We are currently working on an improved Pull Request experience; the project is in progress and should be available as a labs feature in the coming months. While the initial labs feature may not address all performance issues regarding large commits, it will continue to be improved upon over the course of the year. I will update this ticket with directions on how to turn it on once ready.
As can be seen, that feature is still being worked on, but there is no planned release date yet.
Please have a look at the Implementation of New Features Policy for further information on how new features and improvements are prioritized.
We appreciate your understanding.
How looks this feature from Bitbucket side? I need to review a company PR but I can't show diffs. How am I supposed to open it?
Thank you.
This continues to be an annoyance with the Bitbucket pull request UI. Many times, the actual file diff is small, so clearly there is a problem with the Bitbucket implementation. Furthermore, when the diff is not displayed, it obfuscates any comments that other developers added during the pull request code review process; which then requires that every (minimized) diff must be manually opened, to check for comments. Not good.
Not sure how the accepted answer is to point the user to two ignored feature requests one that is over 8 years old and the other that is over 2 years old.The solution is for this to be considered a BUG and for Atlassian to get off their A$$'s and fix this crap. How can they have a source control solution that supports GIT and PR's and it cannot show you a diff that is required for a code review to occur which is one of the many great things about GIT and PR's. This is a blocking issue that prevents code reviews from occurring within the PR itself where they belong.Atlassian time and time again ignores real bugs, treats them as "Suggestions" and then ignores them for years and years. Even bugs they agree to accept as bugs typically get the same treatment.We as the users need to talk to the person in the company who controls the decision of what source control vendor we use, especially for cloud-based ones. Then we need to get them to switch to GitHub or Azure DevOps both of which do not have this issue and have always worked flawlessly for me at other companies that used them.We as real users are typically not in control of the decisions like this and are forced to use the tools provided. This is sad but a reality at many companies. It is easier than ever to migrate from one GIT based cloud provider to another and not lose any history.We should find ways to show that Atlassian products are a bad value and they cost the company more money than they are aware of based on lost productivity they cause on a daily bases from Bitbucket and Jira being the worst offenders but Confluence isn't far behind.
I have got this issue today. Have you already released any patch?
Thank you
It looks like you're new here. Sign in or register to get started.
