3 ms·
>> Merging pull requests takes longer than it used to, but it is important to realize that merges happen asynchronously in the background and so you do not need
by ian85 5y ago
>> Merging pull requests takes longer than it used to, but it is important to realize that merges happen asynchronously in the background and so you do not need to wait for a pull request to be merged. If you navigate away, it will finish while you are doing other things. We're updating the UX to make this clear.
This is terrible, sounds like this is the new norm. If I have to merge in 10 pull requests I can't wait 5 minutes per PR to see if there are going to be any merge conflicts, etc.
Ever since this popped up I'm seriously considering migrating everything away from bitbucket because of how slow merging is.
- dkarp 5y agoyes, this is driving me nuts. I regularly have to merge 3-4 pull requests and it's taking over a minute for each. This used to be a few clicks and now it's a 5-10 minute job making sure everything has merged correctly. Then you go and merge dev into a feature branch and have to wait another minute. I cannot believe this isn't a priority at Bitbucket and we're being told to get used to it and that the UI will hide it. I've been putting off migrating to Github because we use a lot of integrations, but Bitbucket has suddenly become a pain point where it was okay before.