You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/001-multi-provider-taskstoissues/spec.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
-`spec.taskstoissues` (alias of `adlc.spec.taskstoissues`)
11
11
12
12
It reads a config file to determine target backend, then branches to provider-specific issue creation instructions — all within a single template file.
13
-
**Success Criteria**: All four target providers (GitHub, GitLab, Linear, Jira) can create issues from `tasks.md`. Backward-compatible default to GitHub. No template proliferation.
13
+
**Success Criteria**: All four target providers (GitHub, GitLab, Linear, Jira) can create issues from `tasks.md`. Backward-compatible default to GitHub. No template proliferation.
14
14
**Constraints**: Must not break existing GitHub-only users. Must not depend on new extension system features. Must work with both MCP-based and REST-based providers. Single `.md` file — no template fragments.
0 commit comments