Add a Docker-isolated GitHub software factory automation loop
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #557 by @neubig — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by inspecting the existing issue-to-PR, reviewer, and iterate automations, then trace how they handle polling, credentials, Docker conversations, evidence, and merging. Validate the design against a disposable public repository first. Done means the four roles, deduplication, isolation, acceptance checks, stale-evidence rejection, resource limits, and cleanup satisfy every listed acceptance criterion.
Written by the indexing model from the issue text.
Description
Desired Behavior
The existing issue-to-PR, reviewer, and iterate automations do not form an unattended delivery loop with triage, explicit acceptance criteria, isolated credentials, tested review evidence, and automatic merge.
Acceptance Criteria
- Four reusable roles: issue triage, implementation, independent review/test, and periodic recovery/merge.
- Polling deduplicates by issue state and PR head SHA, and handles an initially empty repository.
- Coding and review use distinct Docker conversations and publish traceable evidence.
- Role-scoped GitHub access restricts each automation to one configured repository and necessary operations.
- Merge requires independent acceptance and successful tests for the current head and refuses stale evidence or failing checks.
- Resource limits and cleanup bound concurrent work.
Readiness
ready-for-dev. The software factory is initially validated against a disposable public repository before general catalog rollout.
- Dominant language
- Python
- Stars
- 184
- Forks
- 137
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 46
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenHands/extensions
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenHands/extensions#973 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenHands/extensions#970 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#969 ·
Maintainers usually reply within 1 day
-
Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+Possibly taken @sumitvairagar claimed this 3 days ago. Openpriority:medium ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
OpenHands/extensions#963 ·
Maintainers usually reply within 1 day
All issues in OpenHands/extensions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
backend/local comp/tools P2 tool/terminal type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#158788 ·
Maintainers usually reply within 1 day