This repository has been archived by the owner on Dec 10, 2024. It is now read-only.
feat: add Bitbucket Cloud and Server import endpoints #1979
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pwlandoll
force-pushed
the
feat/1629-bitbucket-import
branch
from
2c9b477 to
1a9af23
Compare
pwlandoll
force-pushed
the
feat/1629-bitbucket-import
branch
from
1a9af23 to
18b8815
Compare
pwlandoll
changed the title
|
Unmarked as "draft" since I was able to at least verify that the API responses were as expected and handled correctly. |
svanharmelen
force-pushed
the
feat/1629-bitbucket-import
branch
from
9d4507b to
449f521
Compare
svanharmelen
approved these changes
Aug 8, 2024
This was referenced Aug 9, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This expands the changes in #1942 to fully implement #1629 and #1859 by adding functionality for the Bitbucket Cloud and Server repository import endpoints.
Although the API documentation does not specify expected responses, the OpenAPI specification looks like it gives sufficient information.
This is marked as a "draft" for now since I have not yet tested against real Bitbucket or GitLab instances.