Add Azure DevOps integration support #3902
Labels
area-autolinks
Issues or features related to autolinks
area-integrations
Issues or features related to integrations
area-launchpad
Issues or features related to Launchpad
Milestone
Add full support for Azure DevOps integrations -- prs, issues, and autolinks (launchpad, start work, etc)
Steps (checkpoints)
Follow-ups:
Additional info
1
some limitations we should be aware of working with Azure and the shared provider library
Today (and this is what GKDev does), to get my Azure PRs for Launchpad, I have to:
it seems for the time being like all of these calls are a minimum necessity to get you all your Azure PRs for Launchpad. This should all be abstracted away into the shared provider library, but as of this moment it isn't. Probably too big of a lift to move the entire procedure into the library this week, but I can ping Jacob or Jose about doing it and we can update it later (not a blocker for release)
We may want to do at least 1, 2 and 3 on connection to Azure, and cache them locally in the integration, just like we do today with the Jira Cloud integration, because those things aren't likely to change very often. Then we can use the cache to eliminate steps 1, 2 and 3 from the individual queries
2
Found out that shared provider library doesn't support head repository info on PRs for Azure DevOps. We need that critically in order to support finding and opening the PR's repo i.e. from Launchpad and other places.
Made a PR to the library: https://github.com/gitkraken/provider-apis-package-js/pull/208/files
Once that is in and the version is bumped, we can update on our end.
(Also found out that gkdev was treating the base repo as the head repo, so I gave them a heads up too)
The text was updated successfully, but these errors were encountered: