Add a Docker-isolated GitHub software factory automation loop

Open
#556 2 comments 0 reactions 0 assignees View on GitHub

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
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, github, python

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

enhancement ready-for-dev
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/extensions

All issues in OpenHands/extensions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.