Automations should be able to use /orchestrate to access multiple repos
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Feature summary
Allow multiple repos for automation
### What problem are you trying to solve?
I have to choose a single repo when creating an automation. I can give it my own orchestration routine as part of the prompt but it would be better to just be able to select multiple repos for orchestration in the UI.
### Proposed solution
I would like to see the ability to select multiple repos for an automation like you can for a chat and have it run the /orchestrate skill to access all the repos and make changes as necessary.
### Workflow impact
Anyone who is in a multi repo environment (majority I suspect) and is trying to use the automations feature.
### Installation context
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by tracing the automation creation UI and the existing /orchestrate workflow. Define how multiple repositories are selected and how the automation gains access to all of them, then verify the complete multi-repository automation flow works as described.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100