Skip to content

docs: clarify slice-1 context-PR base and restore #2548 cross-ref #3325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jwbron merged 4 commits into from
Jun 27, 2026
Merged

docs: clarify slice-1 context-PR base and restore #2548 cross-ref #3325

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e3f6f35
docs: fix stale orchestrator.md anchors in concurrent-execution.md [d…
jwbron Jun 26, 2026
5d63585
Fix checks: apply automated formatting fixes
Jun 26, 2026
b299cd8
Merge remote-tracking branch 'origin/main' into egg/egg-exec-20260626…
jwbron Jun 26, 2026
0160724
Fix checks: restore #2548 cross-ref and tie slice-1 base to context b…
james-in-a-box[bot] Jun 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/guides/concurrent-execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1019,7 +1019,9 @@ obligations) so reviewers approaching any slice PR see the strategic
direction below it.

The pipeline work branch is itself the context PR's head — there is no
separate `egg/<id>/context` doc-only branch. The open path is a single
separate `egg/<id>/context` doc-only branch, so slice-1's base resolves
to `egg/<id>/work` (the context PR head) rather than stacking onto an
`egg/<id>/context` branch. The open path is a single
idempotent gateway call: `GatewayClient.lookup_open_pr("egg/<id>/work", base)`
runs `gh pr list --head <branch> --base <base> --state open --json
number` first; on hit, the existing PR number is reused, on miss
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/orchestrator-cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -647,7 +647,7 @@ All five subcommands honour `EGG_ORCHESTRATOR_URL` and `EGG_LIFECYCLE_SECRET` fo

## Context PR Surfaces ([#2777](https://github.com/jwbron/egg/issues/2777))

Slice-aware pipelines (issue-mode pipelines with `contract.slices`) open the **Context PR** — `egg/<pipeline_id>/work → main` — up-front at the plan→implement boundary, hard-required and idempotent (#2777). See [Orchestrator Architecture: Context PR (slice-aware mode)](../architecture/orchestrator.md#context-pr-slice-aware-mode-2777) and the [Concurrent Execution Slice PR Stack](../guides/concurrent-execution.md#slice-pr-stack) section for the full mechanics. The Context PR is orchestrator-authored; `egg-orch` does **not** ship dedicated `--context-branch` / `--context-pr` flags. Operators inspect the Context PR through the same surfaces used for any other contract metadata:
Slice-aware pipelines (issue-mode pipelines with `contract.slices`) open the **Context PR** — `egg/<pipeline_id>/work → main` — up-front at the plan→implement boundary, hard-required and idempotent (#2777). The up-front context-PR mechanism originated in [#2548](https://github.com/jwbron/egg/issues/2548) and was hardened into the current orchestrator-authored, idempotent form by #2777. See [Orchestrator Architecture: Context PR (slice-aware mode)](../architecture/orchestrator.md#context-pr-slice-aware-mode-2777) and the [Concurrent Execution Slice PR Stack](../guides/concurrent-execution.md#slice-pr-stack) section for the full mechanics. The Context PR is orchestrator-authored; `egg-orch` does **not** ship dedicated `--context-branch` / `--context-pr` flags. Operators inspect the Context PR through the same surfaces used for any other contract metadata:

```bash
# Inspect the contract's pr fields. The top-level --pipeline-id flag goes BEFORE
Expand Down
Loading