-
Notifications
You must be signed in to change notification settings - Fork 503
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
Bitbucket support #562
Comments
As I could see from the discussion in #313 the GitLab work has been based on @tjheslin1 work for Bitbucket. A colleague and I are giving it a try today to base the actual implementation for Bitbucket on @daddykotex work and see how far we will come. |
@dpfeiffer Jolly good! Great news. Unfortunately I wasn't able to dedicate more time after my initial start at the problem! @daddykotex has done an excellent job! |
@fthomas How do you like to proceed on integrating the generalization of the VCS? While working on this ticket, we encountered that some abstractions (that are tied towards the GitHub API) need to be reworked slightly to be more general and work as well with the Bitbucket API. Before we start to polish the code that we created on Friday it would be great to sort this out. Next week I will give it a try at work. |
@dpfeiffer I think it makes the most sense to base your work on the |
@fthomas I based it directly on @daddykotex I finished a rough implementation yesterday which i would like to evaluate internally first (first trial runs seemed to work fine) and of course polish (topic/gitlab...dpfeiffer:topic/bitbucket) |
Same motivation as GitLab support #313.
Also to track already ongoing efforts in master...tjheslin1:bitbucket
The text was updated successfully, but these errors were encountered: