konveyor / konveyor/agentic-controller
Continuation runs: re-enter an existing target branch
- Dominant language
- Go
- Stars
- 2
- Forks
- 12
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 41
Description
Controller/entry-point support for continuation runs: a new run pointed at an existing target branch pulls it (instead of creating it) and is told it continues prior work — internally identical to "stage 2 of a workflow."
Cut-line note: high demo value, not load-bearing — first to slip if the sprint math fails.
Done when:
- An E2E run against an existing branch resumes from its head and pushes on top of the prior work.
Depends on: none.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the controller entry point for continuation runs and trace how a target branch is created or selected. Run or add the E2E scenario for an existing target branch; done means the run resumes from that branch's head and pushes new work on top of it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100