Skip to content

Repin the self-callers to the published name admission - #96

Merged
hyperpolymath merged 1 commit into
mainfrom
marina/optimistic-cray-js64k7
Nov 10, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
marina/optimistic-cray-js64k7

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

This is follow-up 1 of #94. The owner asked for the repin and for the two Minor review items from #94.

Why

#94 is on main as 1fd5e6371a50f0fc3687206a5adca0cdf7b39aa6. From that commit the suite admits hyperpolymath/proven-cicd-and-workflows as a caller name. A self-caller can use the new name only with a pin that includes that admission and is on main. That commit is the first one.

What

Repin

File Before After
.github/workflows/secret-scanner.yml hyperpolymath/proven-cicd @ a12b2b4 hyperpolymath/proven-cicd-and-workflows @ 1fd5e63
.github/workflows/creusot-live-canary.yml new name @ 6c6d772, which refuses that name new name @ 1fd5e63
  • The canary's ancestry check and both literals in tests/creusot-live-canary.sh move with the call.
  • config/workflow-lock-scope.json: the reason text named the PR70 pin. It now names a published suite commit.
  • After this change, no workflow in this repository calls the proven-cicd repository.

Two Minor items from the #94 review

  • README.adoc: one sentence tells consumers to pin a commit that contains the migrated main-estate-audit.yml (1fd5e63 or later).
  • templates/track-estate-audit.yml: the tracker now extracts and replaces a SHA only in a complete uses: reference to this suite under hyperpolymath. The earlier pattern had no owner prefix, and sed replaced the SHA in the whole file.

Hosted checks on 3e5f763

All 27 check runs completed: 25 passed, and CodeRabbit and CodeQL were neutral.

  • Scanner under the new name: scan / gitleaks, scan / rust-secrets and scan / shell-secrets pass (run 42859834371).
  • Creusot canary at the new pin (run 42859834214): Detect Creusot obligations, Creusot theatre gate, Creusot proofs (cargo creusot prove) and Creusot verdict all pass. The proof job ran for about 9 minutes. These checks failed on Admit the renamed repository and call it by its new name #94, where the pin refused the new name.
  • Locked fixture and published source passes, so the new pin is on main.

Evidence (local)

  • Tracker step on fixtures. The fixtures hold 3 suite callers (bare, single-quoted, double-quoted) and 3 other references at the same SHA (a fork, a near-name owner, an unrelated action).
    • New step: the 3 suite callers move to the new name and the new SHA. The other 3 references stay. A second run reports changed=0.
    • Step from main: it rewrites all 3 of the other references.
  • tests/suite-source-compatibility.sh and tests/published-scanner-pin.sh pass. They ran through an adapter that drops -o=json, because the yq on this machine is the jq-based one.
  • Both --check builders pass.
  • The pin is an ancestor of origin/main.

After merge

🤖 Generated with Claude Code

https://claude.ai/code/session_0136P7ZmAsYpFA9gxfQLF3F6

PR 94 is on main as 1fd5e63. From
that commit the suite admits hyperpolymath/proven-cicd-and-workflows
as a caller name. Move the two self-callers to that name and that
commit:

- secret-scanner.yml called hyperpolymath/proven-cicd at a12b2b4.
  After this change no workflow in this repository calls the
  proven-cicd repository.
- creusot-live-canary.yml called the new name at 6c6d772, whose
  resolver refuses that name. Move the call, the ancestry check and
  both literals in tests/creusot-live-canary.sh together.
- config/workflow-lock-scope.json: the reason text named the PR70
  pin. Make it name a published suite commit.

Two minor review items from PR 94:

- README.adoc: tell consumers to pin a commit that contains the
  migrated main-estate-audit.yml (1fd5e63 or later).
- templates/track-estate-audit.yml: extract and replace a SHA only in
  a complete uses: reference to this suite under hyperpolymath. The
  earlier pattern had no owner prefix, and sed replaced the SHA in the
  whole file.

Tracker step run on fixtures (bare, single-quoted and double-quoted
callers; a fork reference, a near-name owner and an unrelated action
at the same SHA): the 3 suite callers move to the new name and SHA,
the other 3 references stay, and a second run reports changed=0. The
step from main rewrites all 3 of the other references.

Local checks: tests/suite-source-compatibility.sh and
tests/published-scanner-pin.sh pass through a yq adapter; both --check
builders pass; the pin is an ancestor of origin/main. The canary and
the yq-based tests need the hosted run.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmAsYpFA9gxfQLF3F6
Signed-off-by: Claude <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 20 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 2d929ae1-089e-4265-9030-e58e57580ce2
Commits

Reviewing files that changed from the base of the PR and between 1fd5e63 and 3e5f763.

Files selected for processing: 6

  • .github/workflows/creusot-live-canary.yml
  • .github/workflows/secret-scanner.yml
  • README.adoc
  • config/workflow-lock-scope.json
  • templates/track-estate-audit.yml
  • tests/creusot-live-canary.sh
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 10, 2026 16:58
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-10T16:58:09.304561Z
We couldn’t complete this review. Comment @codex review to try again.
3e5f763 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@hyperpolymath
hyperpolymath merged commit 24b244a into main Nov 10, 2026
26 checks passed
@hyperpolymath
hyperpolymath deleted the marina/optimistic-cray-js64k7 branch November 10, 2026 16:58
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.

3 participants