Skip to content

integration: submit tip downstacks alongside the integration branch#1254

Open
ed-irl wants to merge 3 commits into
ed-irl/integration-accept-incomingfrom
ed-irl/integration-submit-tip-stacks
Open

integration: submit tip downstacks alongside the integration branch#1254
ed-irl wants to merge 3 commits into
ed-irl/integration-accept-incomingfrom
ed-irl/integration-submit-tip-stacks

Conversation

@ed-irl

@ed-irl ed-irl commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

'gs integration submit' previously only force-pushed the integration
branch. Since the integration branch is the union of its configured
tips, publishing it implies publishing those tips. Otherwise users had
to remember to separately submit each tip stack — easy to forget when
gs ints is meant to be the one-shot "publish the integration" command.

For each configured tip, walk its downstack (trunk-exclusive,
dedup'd), then run SubmitBatch in trunk-first topological order so
bases are pushed before the branches that depend on them. After the
tip-stack batch completes, push the integration branch itself with
its existing force-with-lease semantics.

All the standard submit flags now apply to gs ints (--fill,
--no-publish, --update-only, etc.), so users can keep the previous
"push the branch only" behavior with --no-publish if desired.

@ed-irl

ed-irl commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator Author

@ed-irl ed-irl force-pushed the ed-irl/integration-accept-incoming branch from 1c9f8de to 1128e43 Compare June 13, 2026 13:40
@ed-irl ed-irl force-pushed the ed-irl/integration-submit-tip-stacks branch from dc1dd02 to b0668b4 Compare June 13, 2026 13:40
@ed-irl ed-irl force-pushed the ed-irl/integration-accept-incoming branch from 1128e43 to 7474ad2 Compare June 15, 2026 09:53
@ed-irl ed-irl force-pushed the ed-irl/integration-submit-tip-stacks branch from b0668b4 to 784a6ab Compare June 15, 2026 09:53
ed-irl and others added 2 commits June 23, 2026 11:43
'gs integration submit' previously only force-pushed the integration
branch. Since the integration branch is the union of its configured
tips, publishing it implies publishing those tips. Otherwise users had
to remember to separately submit each tip stack — easy to forget when
gs ints is meant to be the one-shot "publish the integration" command.

For each configured tip, walk its downstack (trunk-exclusive,
dedup'd), then run SubmitBatch in trunk-first topological order so
bases are pushed before the branches that depend on them. After the
tip-stack batch completes, push the integration branch itself with
its existing force-with-lease semantics.

All the standard submit flags now apply to gs ints (--fill,
--no-publish, --update-only, etc.), so users can keep the previous
"push the branch only" behavior with --no-publish if desired.
@ed-irl ed-irl force-pushed the ed-irl/integration-accept-incoming branch from 2b559fb to 7090d21 Compare June 24, 2026 01:33
@ed-irl ed-irl force-pushed the ed-irl/integration-submit-tip-stacks branch from 6e42b20 to 1df251c Compare June 24, 2026 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant