jredmond

This is the safer bet. The host should offer to restore from their own backups, but some customers may have already taken care of their own stuff.

Updated link: https://dpb.bitbucket.io/hacker-school-and-how-we-learn.html

I don't have any hard evidence, but I suspect that the people who have already jumped ship from GH only did so with solo projects or with very small teams. The switching cost for those people/teams is always going to be pretty low.

The Bitbucket pricing on that page is outdated - the updated version is https://bitbucket.org/product/pricing?tab=cloud .

Did you see https://status.bitbucket.org/incidents/vgfrs5y83kqb ?

Looks like a good project. You should probably mention very, very early on in your docs, though, that this is for Bitbucket Server (self-hosted) and not for Bitbucket Cloud (bitbucket.org).

That depends - is that data encrypted on your system? Since git is decentralized, there's a chance that any plain-text copy (such as a clone on your system) could be compromised. Keybase even addresses this in the FAQ, to an extent:

> What if my computer is compromised?

> Your work is only as safe as your endpoints, so we can't help you there.

This applies regardless of host or protocol, BTW, and it isn't even specific to computing. (It doesn't matter how many locks you have on your front door if you leave the back door propped open.)

You can set up an application-specific password and limit its scope: https://blog.bitbucket.org/2016/06/06/app-passwords-bitbucke...

I can't answer the PM questions, but the Bitbucket blog is hosted externally, not on Bitbucket itself.

The Atlassian account should not affect any SSH keys you may have added.

If you're logged in, there's a "Vote for this issue" link next to the number of votes in the info box at the top of the issue. (The UI will strongly discourage "+1" comments unless they have something else to say.)