Repository navigation
feat(tasks): import issues from GitLab - #1552
leoisadev1 wants to merge 1 commit into
Conversation
Parse gitlab.com issue and work item URLs, including nested groups, fetch them through the public GitLab API, and add a GitLab option to both import dialogs. Fixes worknenjoy#1097
6194295 to
51cbe57
Compare
|
Thanks for this — the GitLab connector and the import-side work here is a good start, and the title/status sync-on-fetch is genuinely well done. It's not mergeable as-is yet, though. Two things need to land first:
On top of that, We've opened #1563 to work through all of this, and are asking in #1097 for provider-specific verification on the identity/OAuth side. Could you hold off on further work here until that's settled, so effort isn't spent on a shape that ends up changing? We'll follow up on this PR once the architecture discussion lands. |
Summary
Gitpay can import GitHub and Bitbucket issues. This adds GitLab.com so a URL like https://gitlab.com/mission-center-devs/mission-center/-/issues/3 (the example on #1097) creates a task.
What changed
gitlab.com/www.gitlab.comissue URLs, including nested groups,/-/issues/:id, and/-/work_items/:idGitlabConnectclient for the public REST API (/projects/:path/issues/:iid, project metadata, languages)openedto gitpayopenanddescriptionto the issue body the UI already expectsTests
Mocha coverage of the parser plus a nock of the shipped
GitlabConnectclient (12 passing).Closes #1097