[OrlaM]

Fixes #7057.

Adds github.submit_patch, the GitHub equivalent of phabricator.submit_patch. The agent records the action during the run. When it is applied, hackbot-api pushes the run's commits to a hackbot/<run_id> branch of the agent's source repository and opens a draft PR against its default branch. The PR's url goes in the action result, so later actions can reference it.

How it works

hackbot-api has no checkout or git binary, so it can't git push. This follows the Phabricator diff and the try push: the git work happens in the agent's container, and hackbot-api only calls the service's API.

• Agent side: publish_changes writes changes/github_commits.json when a github.submit_patch is recorded, next to the existing changes artifacts. build_github_commits in changes.py builds it from the commits since the published base. It includes uncommitted work, through the same WIP commit the other artifacts use, and records for each commit its message, author and changed files.
• Apply side: github_handler.SubmitPatchHandler replays those commits through GitHub's Git Data API (blobs, trees, commits, then a branch ref) and opens the draft PR. Commits keep their original author, and the GitHub App commits and signs them. The installation token is narrowed to the one repository, with contents: write and pull_requests: write.
• Retries: a failed action can be applied again, so the handler moves the run's branch if it already exists and reuses a PR already open from it.
• Patch types: github.submit_patch is added to hackbot-api's PATCH_ACTION_TYPES, so a run that leaves changes without submitting them is still flagged. The runtime gets its own GitHub PATCH_ACTION_TYPES, kept separate from the Phabricator one so that a GitHub submission doesn't also build a Phabricator diff.
• Docs and UI: a catalog row in docs/hackbot/actions.md, and a pull request preview (title and body) on the run page.

Tests

• hackbot-api: pytest tests/ passes (524). The new test_github_handler.py drives githubkit against a fake api.github.com built on httpx.MockTransport. It covers the full flow, an empty body, a retry that reuses the branch and PR, a non-GitHub repository, a missing artifact, GitHub rejecting a call, and the App not being configured.
• hackbot-runtime: pytest tests/ passes (349). It covers the tool, build_github_commits against real git repos (multiple commits, uncommitted work, deletions, file modes, binaries, renames, no changes) and publish_changes gating.
• pre-commit passes on the changed files.

This hasn't been run against a real GitHub repository yet.

Risks and follow-ups

• The target repository comes from the [source].repo_url inside the agent-built artifact. That's the same trust model as changes.json, and the token only works where the App is installed. A server-side allowlist of repositories could be added later.
• The PR always targets the default branch; there is no base-branch parameter.
• No agent enables the action yet. bug-fix would also need prompt changes before using it.
• Each changed file in each commit is a separate API call, made one at a time as GitHub recommends for creating content. Very large changes will be slow.
• A path that isn't valid UTF-8 makes the artifact build fail. That gets logged and the artifact is skipped, so applying the action then fails.

[Copilot]

🟡 Changes recommended

The agent-writable artifact controls both the target repository and credential installation, allowing a compromised run to create branches and PRs in other repositories where the App is installed.

2 open issues

• Bind target repository and installation to trusted configuration · New
• Request workflow permission for workflow-file changes · New

What changed in this PR

Adds github.submit_patch, the GitHub equivalent of Hackbot’s Phabricator submission action, addressing #7057. Agents record a submission during a run; hackbot-api later recreates the commits and opens a draft pull request.

Changes:

• Adds the recording tool and GitHub-specific commit artifact generation.
• Registers an apply-side handler that creates commits, manages the run’s branch, and reuses an existing PR on retries.
• Adds runtime and API tests, action documentation, and a UI preview.

File	Description
services/​hackbot-ui/​components/​RunDetail.tsx	Previews the PR title and body.
services/​hackbot-api/​tests/​test_github_handler.py	Tests GitHub API calls, retries, and failures.
services/​hackbot-api/​app/​action_handlers/​registry.py	Registers the handler and patch action type.
services/​hackbot-api/​app/​action_handlers/​github_handler.py	Recreates commits and opens draft PRs.
libs/​hackbot-runtime/​tests/​test_github_actions.py	Tests action recording and tool exposure.
libs/​hackbot-runtime/​tests/​test_context.py	Tests artifact publishing and commit naming.
libs/​hackbot-runtime/​tests/​test_changes.py	Tests commit serialization and file changes.
libs/​hackbot-runtime/​hackbot_runtime/​context.py	Publishes GitHub artifacts for recorded submissions.
libs/​hackbot-runtime/​hackbot_runtime/​changes.py	Builds the GitHub commit payload.
libs/​hackbot-runtime/​hackbot_runtime/​actions/​github.py	Defines the submission recording tool.
libs/​hackbot-runtime/​hackbot_runtime/​actions/​claude_sdk.py	Exposes the tool through the Claude SDK integration.
libs/​hackbot-runtime/​hackbot_runtime/​actions/​__init__.py	Exports GitHub actions.
docs/​hackbot/​actions.md	Documents the action and submission flow.

_{Review effort: Balanced}