I cannot express nearly enough how much I hate whatever was recently done to the Create Pull Request page.
How the heck do I set the option to VIEW MORE THAN ONE FILE AT A TIME????
When I am in the process of creating a Pull Request, I have to review my files before clicking Create button. Sometimes there are NUMEROUS files, and having to click each .. and... ev ... ery ... single ... one ... is a painful and arduous task.
I don't know to who or why this was deemed a need. For me, this slows down my process and, well, is quite frankly a nuisance that gets in my way of quickly completing my tasks.
To further exacerbate the issue, after the PR is created, when I go to view it I get:
"This is a large pull request. Large pull requests can only be viewed by loading files individually." Folks, I hardly call 19 files and 258 updated lines of code a "large" PR. I've seen and dealt with much bigger. For PRs like this I just need to be able to scan the files and go.
Please, please is there an option that I can set to turn this feature off? Please?
Thank you.
Hi Kerry and welcome to the community.
If you open an existing pull request and select the Settings link (see screenshot)
for the option Load files, which one is selected? All at once or Individually?
If Individually is selected, can you change it to All at once, save the options, and check if all files are shown the next time you create a PR?
Kind regards,
Theodora
Hello Theodora. Thank you for your reply.
So I found a merged PR (there were none open at the time), and here is what I saw:
It appears the option is already selected. When I create a new PR, then click "Create Pull Request", the page refreshes, and I see this:
So a few things baffle me:
1) The Global setting is "All at once", and I'm not seeing all my files all-at-once.
2) Why on earth would I need to dig up another PR for a setting I need in the PR I'm trying to create? It would be far more helpful to have a setting available and accessible to me where I'm at.
3) Once the PR is created, why do I see a message saying this is a "large pull request"? It's only 16 files. This doesn't make sense to me. Interestingly, if I refresh the page, the message goes away and I can see all the files. But it would be so helpful to me to not have to take that extra step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kerry,
Thank you for the info.
2) Why on earth would I need to dig up another PR for a setting I need in the PR I'm trying to create? It would be far more helpful to have a setting available and accessible to me where I'm at.
This setting should be applied to all PRs for your user. So, if you set it for one PR, it will be the same for all the other PRs you access and also for the Create Pull Request page.
If the PR diff is within our limits, we would need to check one such PR where the issue is reproducible to investigate further. This is something I cannot do without a support ticket (we need a support ticket to access a repo).
You can create a ticket with the support team and provide the link of a PR where files do not load all at once (even though you have that setting enabled) and where you see the message that the PR is large.
You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation. The support ticket will be visible only to you and Atlassian staff, so any info you post there won't be publicly visible.
Please feel free to let me know if you have any questions.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.