Skip to content

✨ [feat] workspace: drive several repos from one board - #96

Closed
EricEchemane wants to merge 1 commit into
EricTechPro:mainfrom
EricEchemane:feat/multi-repo-workspace
Closed

EricEchemane wants to merge 1 commit into
EricTechPro:mainfrom
EricEchemane:feat/multi-repo-workspace

Conversation

@EricEchemane

Copy link
Copy Markdown
  • A config with a repos map resolves into one single-repo config per repo
  • Cards are identified as <repo>#<n>, because issue numbers repeat across repos
  • ## Blocked by accepts <repo>#<n>; an unknown repo counts as blocked
  • Key the card cache by repo so a move cannot hit another repo's issue
  • Share one GitHub halt file across the workspace; status prints one board per repo
  • Codex lanes and the claude-p backend refuse workspace configs (exit 78)

- A config with a `repos` map resolves into one single-repo config per repo
- Cards are identified as `<repo>#<n>`, because issue numbers repeat across repos
- `## Blocked by` accepts `<repo>#<n>`; an unknown repo counts as blocked
- Key the card cache by repo so a move cannot hit another repo's issue
- Share one GitHub halt file across the workspace; `status` prints one board per repo
- Codex lanes and the `claude-p` backend refuse workspace configs (exit 78)
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant