Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Bitbucket to Keybase #19

Closed
mark-adams opened this issue Mar 19, 2015 · 6 comments · Fixed by #18
Closed

Add support for Bitbucket to Keybase #19

mark-adams opened this issue Mar 19, 2015 · 6 comments · Fixed by #18

Comments

@mark-adams
Copy link
Contributor

Atlassian Bitbucket launched their Snippets feature today which allows developers to post arbitrary pieces of code publicly. With the addition of this feature, users should now be able to create Bitbucket proofs.

Documentation for the API is available here: https://confluence.atlassian.com/display/BITBUCKET/snippets+Endpoint

maxtaco added a commit that referenced this issue Sep 22, 2015
Got a version working and tested with server-side support
maxtaco added a commit that referenced this issue Sep 22, 2015
@virtualdxs
Copy link

When does this come into the release client?

@kg4zow
Copy link

kg4zow commented Jun 19, 2017

I hate to sound like "me too", but ... any idea when this will make it into the release clients?

@computator
Copy link

Just wondering what happened to this since it was merged nearly 4 years ago.
@maxtaco

@maxtaco
Copy link
Contributor

maxtaco commented Jul 25, 2019

we now have a new system to do this!

https://keybase.io/docs/proof_integration_guide

@computator
Copy link

I did see that, however that requires us to wait on bitbucket to add support. If we already have code written for bitbucket that uses snippets, just like GitHub has explicit code for gists, then why not use it?

@maxtaco
Copy link
Contributor

maxtaco commented Jul 25, 2019

There's a lot of tooling around doing it the old way that never got done because there wasn't enough interest internally and externally. The new way has us automating the tooling but does require the other side to help out. But it lends to a smoother experience. We're happy to help them out if they'd be interested in this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants