Description
Problem
OpenCode’s GitHub Action flow can create pull requests automatically, which is a useful safety boundary. The problem is that the PR title does not appear to have an explicit, structured contract.
From the behavior I observed, the PR title seems to be generated by a separate summarization pass over the agent response, rather than being taken from a dedicated structured field. That makes the title fragile: it can drift toward operational or status-like wording instead of a clean reviewer-facing summary.
Why this matters
A PR title is persistent repository metadata. It should be predictable, concise, and reviewer-facing.
If the action has no explicit title contract, then:
- the model may produce operational or status-like wording instead of a clean summary
- the title can become dependent on prompt phrasing rather than a stable interface
- downstream repository standards become harder to enforce consistently
What I’m asking for
I am not asking to change the automatic PR creation flow.
I am asking for a clear contract for PR metadata, especially the PR title:
- Is there a supported schema or dedicated slot for PR title output?
- If not, should there be one?
- Should the action require a structured PR metadata block, rather than relying on freeform text?
- If the current design intentionally uses a summarization step to derive the PR title, how should that be documented and constrained so titles remain deterministic and compliant with repository standards?
Expected behavior
The system should provide a clear and documented way for the agent to supply a PR title that is:
- single-line
- concise
- reviewer-facing
- separate from operational/status text
Current behavior
The title-generation path appears to be implicit rather than contractual, and the title seems to be derived from a summary of the response rather than a dedicated PR title field. That makes it hard to know what the agent is actually supposed to emit for PR metadata.
Suggested outcome
Please document or introduce an explicit PR title contract for GitHub Action mode, so the agent has a clear place to put the PR title and repositories can reliably enforce title standards.
Plugins
No response
OpenCode version
v1.15.13
Steps to reproduce
Use /oc to ask OpenCode to create a PR
Screenshot and/or share link
Operating System
Ubuntu 24.04 (GitHub hosted Action runners)
Terminal
No response
Description
Problem
OpenCode’s GitHub Action flow can create pull requests automatically, which is a useful safety boundary. The problem is that the PR title does not appear to have an explicit, structured contract.
From the behavior I observed, the PR title seems to be generated by a separate summarization pass over the agent response, rather than being taken from a dedicated structured field. That makes the title fragile: it can drift toward operational or status-like wording instead of a clean reviewer-facing summary.
Why this matters
A PR title is persistent repository metadata. It should be predictable, concise, and reviewer-facing.
If the action has no explicit title contract, then:
What I’m asking for
I am not asking to change the automatic PR creation flow.
I am asking for a clear contract for PR metadata, especially the PR title:
Expected behavior
The system should provide a clear and documented way for the agent to supply a PR title that is:
Current behavior
The title-generation path appears to be implicit rather than contractual, and the title seems to be derived from a summary of the response rather than a dedicated PR title field. That makes it hard to know what the agent is actually supposed to emit for PR metadata.
Suggested outcome
Please document or introduce an explicit PR title contract for GitHub Action mode, so the agent has a clear place to put the PR title and repositories can reliably enforce title standards.
Plugins
No response
OpenCode version
v1.15.13
Steps to reproduce
Use
/octo ask OpenCode to create a PRScreenshot and/or share link
Operating System
Ubuntu 24.04 (GitHub hosted Action runners)
Terminal
No response