Skip to content

Docs: pin GitHub acceptance ref identity #1574

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
BigSimmo merged 4 commits into from
Aug 2, 2026
Merged

Docs: pin GitHub acceptance ref identity #1574

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ef644b7
Docs: strengthen GitHub write-test evidence
BigSimmo Aug 2, 2026
9af4d85
Merge branch 'main' into codex/test-github-integration-after-reconnec…
BigSimmo Aug 2, 2026
38ca65c
Update docs/codex-cloud.md
BigSimmo Aug 2, 2026
8f2ce61
Docs: pin GitHub acceptance ref identity
BigSimmo Aug 2, 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
11 changes: 8 additions & 3 deletions docs/codex-cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,9 +149,14 @@ Suggested GitHub acceptance task:

```text
Read AGENTS.md and docs/codex-cloud.md. Create a task-specific branch, add one harmless
documentation-only line, and offer a draft pull request through the Codex GitHub workflow.
Do not merge. Report whether repository clone, branch publication, and draft PR creation
each succeeded. Remove the draft branch/PR only after I approve cleanup.
documentation-only line, commit it, and record its branch name and full 40-character HEAD SHA.
Use the Codex GitHub workflow to publish that exact existing branch and create a draft pull
request. Do not recreate, rename, amend, rebase, or rebuild the branch or commit. Do not merge.
Report whether repository clone, branch publication, and draft PR creation each succeeded, then
report the expected and published branch names and full HEAD SHAs and whether they match exactly.
If branch publication or draft PR creation succeeds, include its link. For each failed write,
report the failure and state that no link is available. Remove the draft branch/PR only after I
approve cleanup.
```

## Setup and maintenance
Expand Down
Loading