Tom Kane Atlassian Team

Bitbucket Cloud now supports rsa-sha2-256 and rsa-sha2-512 algorithms. The OpenSSH 8.8 client will function without the need for a workaround. The team deployed a fix on Tuesday, Oct 19. After monitoring for two days we are confident that the OpenSSH 8.8 incompatibility has been resolved.

Hi, @Danil. We don't have any immediate plans to implement Excluded files for commit diffs. There is a request for that feature if you would like to comment or vote on int.

Hi @Jerry Gardner. Yes, we recently made the decision to extend the deadline by 30 days (from May 31 to June 30). A team is working to send out an email notification shortly with more details. - Tom (Engineering manager on Bitbucket)

Hi @[deleted], While there is a limit of 200 files for a PR, excluded files aren't counted against that limit. Adding or updating rules after creating a PR should have an immediate effect when you refresh the PR view. It's a long shot but maybe try a hard refresh in case you have some local caching. Can you confirm in your…

@rajb245 Thank you for sharing your success story of migrating 5 repos from Mercurial to Git on Windows. https://community.atlassian.com/t5/Bitbucket-articles/What-to-do-with-your-Mercurial-repos-when-Bitbucket-sunsets/ba-p/1155380/page/4#M256 We know Mercurial use cases are very diverse and our user base can learn a lot…

@esoft-adm it is possible to export issues from one repo and import into another. With that said, you will need to convert the repos to git and then export issues from the hg repo and import the issues in the git repo. Here’s a doc with more…

@philipstarkey The Bitbucket team arrived at our current Mercurial deprecation plan after lengthy research and thorough analysis. We investigated several solutions. Regrettably, due to the infrastructure of the Bitbucket platform, solutions such as supporting Mercurial repos in read-only mode would require similar…

I would like to hear more about your specific use case. Do you (and/or your team) intend to actually review this PR with 5000+ files? You want to approve the changes to files that aren't in the excluded directory? Or are you using PRs as a way to merge a batch of changes but you aren't actually reviewing the diff?

Hi Robert, I apologize that I wasn't notified of your message sooner. Due to technical constraints, we filter out excluded files after the diff is calculated. In the future we plan to filter files before the diff is calculated but it will require changes and upgrades to underlying core components. The feature can still…

Hi Luka, I apologize that I wasn't notified of your message sooner. Bitbucket does not currently support Excluded files settings for more than one repository at a time. One reason we chose to use a text field for the Excluded files setting is so that it's easy to copy/paste from one repository to another. We may consider a…

You can read about this feature on the Bitbucket blog.

That's a great idea. We are gathering feedback and usage metrics on excluded files in the new pull request experience. We also have some improvements we want to add to the feature. After that we may consider supporting excluded files in other diff contexts.

We’ve released a new feature called Excluded files. You can now exclude files in large diffs on pull requests for which you are the admin, so the review process is easier for everyone involved. To enable the new feature, go to the repository containing the pull request and click Settings > Excluded files in the Pull…

Sorry, I don't have enough experience with Ansible or Chef to advise you.

One workaround in the meantime is to have multiple clones of your repo and configure each to deploy to a different region.

The AWS CodeDeploy add-on currently only supports deploying to one location (in one region). If you have a specific need, you can make a feature request here and we will take it into consideration. Note that in order to deploy to multiple regions you must define your application once in each region (if you haven't…

I believe the problem lies with the codedeploy Resource in your IAM policy. { "Effect": "Allow", "Action": [ "codedeploy:*" ], "Resource": "arn:aws:s3:::<S3 Bucket Reference Per Instructions>" }, I tried setting Resource to my S3 bucket and I receive the same error. Various attempts at limiting Resource to one S3 bucket…