Skip to content

chore(occ-deps): update rerun state after 509ae56c - #1591

Closed
github-actions[bot] wants to merge 2 commits into
mainfrom
automation/occ-rerun-state-509ae56c
Closed

github-actions[bot] wants to merge 2 commits into
mainfrom
automation/occ-rerun-state-509ae56c

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated OCC rerun state update for merge 509ae56.\n\nThis PR is opened instead of direct-pushing to protected main.

@jonahgabriel
jonahgabriel enabled auto-merge (squash) May 25, 2026 01:51
@jonahgabriel

Copy link
Copy Markdown
Contributor

Closed as redundant automation noise during merge sweep. This PR only removes the YAML document marker from an already-empty drift/occ_dependency_edges.yaml, carries no dependency-edge state change, and cannot satisfy Receipt Gate because it is non-ticketed automation output.

auto-merge was automatically disabled May 25, 2026 02:29

Pull request was closed

@jonahgabriel
jonahgabriel deleted the automation/occ-rerun-state-509ae56c branch May 25, 2026 02:29
jonahgabriel added a commit that referenced this pull request Jul 3, 2026
…CodeRabbit)

- commit_sha: was a014dac6 (omnimarket PR #1591 head, a FOREIGN SHA not present
  in onex_change_control) -> 13f1144 (real OCC commit on this PR branch).
- probe_command: descriptive free-text -> executable 'gh pr view 3545 ...' matching
  the sibling receipt convention; probe_stdout replaced with the real gh JSON output.

Binding is via pr_number=3545 (unchanged); this corrects the recorded provenance
so the self-binding OCC receipt cites an OCC commit, not a cross-repo SHA.

Evidence-Ticket: OMN-13825
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