Specify base branch when instructing Codex from GitHub issue comments
Open 💬 0 comments Opened Nov 20, 2025 by p-krukenfellner
📝 Description
Enable the ability to explicitly specify the base (target) branch to work on when triggering a Codex task from a GitHub issue (by mentioning @codex in an issue comment).
Currently, the base branch used for the implementation of the issue, as well as any resulting pull requests, defaults to the repository’s default branch.
Use Case
Many teams (including ourselves) use bug, development, feature, ..., branches for adding new work.
Proposal
Support an explicit directive in the issue or comment such as:
base: release/v4.0target-branch: release/v4.0Please use release/v4.0 as the base branch for implementing these changes.