dreampiler/kandev
1
0
Fork 0
Code Issues 43 Pull Requests Actions 6 Packages Projects Releases Wiki Activity

feat: add Azure DevOps integration (#1778)

Browse Source
This commit is contained in:
Carlos Florêncio
2026-07-21 08:40:26 +01:00
committed by GitHub
parent d7c24184cd
commit c2a678b023
174 changed files with 12231 additions and 387 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/public/feature-status.md
+1
View File
@@ -73,6 +73,7 @@ Released builds can lag this page. Check **Settings > System > About** or `kande
| Remote Docker executor | In progress | The type and legacy/direct settings fields are registered, but runtime create/stop return `not yet implemented`, and the current **Settings > Executors** hub does not offer it. |
| GitHub integration | Dependency-bound | Workspace repository scope, issue/PR browsing, actions, watches, presets, reviews, checks, and Gists depend on GitHub auth, scopes, rate limits, and repository permissions. Supported Local Docker, Sprites, and SSH launch paths may receive the globally stored token as `GITHUB_TOKEN`/`GH_TOKEN`; workspace repository scope does not constrain its privileges. |
| GitLab integration | Limited | Global connection plus issue/MR search, browse, and external links are shipped. The current `/gitlab` page cannot launch tasks, and task surfaces do not expose discussions, reply/resolve, full review feedback, or pipeline actions; watches/presets also lack an end-user settings path. |
| Azure DevOps integration | Limited | Azure DevOps Services supports workspace PAT configuration, read-only work-item and pull-request browsing, feedback, task launch, and durable task PR associations. Azure DevOps Server/TFS, Entra OAuth, writes, watches, and webhooks are not supported; neither `gh` nor `az` is required. |
| Jira integration | Limited | Search/browse, supported transitions, launch presets, task launch, and watches require provider credentials. Launch copies data rather than creating a durable association; each watch poll reads only the first 50 JQL matches. |
| Linear integration | Limited | Search/browse, state changes, task launch, and watches require provider credentials. Launch has no preset/durable association; a watch reads 50 matches in provider order or at most 250 with explicit local sorting. |
| Sentry integration | Limited | Multi-instance configuration, issue watches, and current-task issue actions are shipped; there is no top-level browser. Watches read only the newest first page, and the status picker allows multiple selections while the backend accepts at most one. |