Pin a Base Branch for Agent Work on Any Project
Projects can now set a specific branch, like develop, for agents to build on, instead of always using the repository's default branch.
Summary
You can now tell Effigate Command Center which branch your agents should build their work on for a given project — useful for teams that keep their default GitHub branch separate from the branch they actually want new work layered onto.
What You Gain
Until now, every agent task always branched from your repository's own default branch, whatever that happened to be set to in GitHub. Teams that work differently — building on a develop branch before anything reaches their default branch, for example — had no way to tell Effigate Command Center that. Agents had no choice but to target the default branch directly, which didn't match how those teams actually ship code.
Now a project's connected repository can specify its own base branch. Leave it unset and nothing changes — agents keep targeting your repository's real default branch exactly as before. Set it, and every agent task for that project builds on the branch you chose instead.
How It Works
- Open a project's Resources, edit the connected GitHub repository, and set a base branch if you want one other than the default.
- Leave it blank to keep using your repository's actual default branch, with no other change.
- Every new agent task for that project respects this setting automatically going forward.
Where to Find It
Find this under Project → Resources, on the settings for a connected GitHub repository. Available to anyone who can edit a project's resources.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.