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 BitBucket support #3

Open
arusahni opened this issue Jun 13, 2016 · 7 comments
Open

Add BitBucket support #3

arusahni opened this issue Jun 13, 2016 · 7 comments

Comments

@arusahni
Copy link
Owner

arusahni commented Jun 13, 2016

People use this service. Bitbucket has cloud and hosted offerings (much like GitLab). For now, let's target the cloud offering.

What this entails:

  • Adding a new remote
@shorsher
Copy link

shorsher commented Oct 3, 2019

So this would just entail adding a new remote for bitbucket?

@arusahni
Copy link
Owner Author

arusahni commented Oct 3, 2019

Yup, including being able to interface with the Bitbucket API.

@shorsher
Copy link

shorsher commented Oct 3, 2019

OK I'm happy to give it a shot. This seems like a nice project for learning more about rust. Sorry ahead of time if I bug with you any questions :D

@arusahni
Copy link
Owner Author

arusahni commented Oct 4, 2019

No worries! Best of luck :-)

@arusahni arusahni assigned arusahni and shorsher and unassigned arusahni Oct 5, 2019
@shorsher
Copy link

shorsher commented Oct 8, 2019

Do you have a preference for support for bitbucket cloud vs server first? Regular (public) bitbucket.com does not require authentication at all. Bitbucket server uses personal access tokens, while Bitbucket cloud uses "app passwords"[0].

0: https://confluence.atlassian.com/bitbucket/app-passwords-828781300.html

Just wanted your input.

@arusahni
Copy link
Owner Author

arusahni commented Oct 8, 2019

Interesting... let's go with Bitbucket Cloud for now - it seems to be the more popular option, and hopefully future versions can be generalized (much as git-req does with GitLab). Thanks for checking in!

@arusahni
Copy link
Owner Author

arusahni commented Aug 24, 2020

Hi @shorsher - since it's been a while, I'm going to unassign the issue. Feel free to ask for it to be assigned back if you think it's something you're going to pick back up.

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

No branches or pull requests

2 participants