fix(ci): publish the canonical hypatia / Hypatia Neurosymbolic Analysis context - #71
Merged
Merged
Conversation
…is context The required status check on this repository is 'hypatia / Hypatia Neurosymbolic Analysis', but the workflow here is the old inline implementation (job id 'scan', name 'Hypatia Neurosymbolic Analysis'), which publishes the bare check name 'Hypatia Neurosymbolic Analysis'. A required check is matched by string equality, so the required context can never be satisfied and every pull request is blocked while the board shows green. This replaces the inline scanner with the estate-canonical thin wrapper: job id 'hypatia' calling hyperpolymath/standards hypatia-scan-reusable.yml, pinned to this repository's own standards pin (fad242d35291) - the same SHA its governance wrapper already uses. Grants match the callee's declared set exactly (actions: read, contents: read, security-events: write).
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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. Comment |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| }); | ||
| hypatia: | ||
| uses: hyperpolymath/standards/.github/workflows/hypatia-scan-reusable.yml@fad242d35291de1898242d6737ba02b74a59a2f2 | ||
| secrets: inherit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ruleset on this repo requires the context
hypatia / Hypatia Neurosymbolic Analysis, but the workflow here is the old inline scanner: job idscan, display nameHypatia Neurosymbolic Analysis, which publishes the bare check nameHypatia Neurosymbolic Analysis. Required checks match by string equality, so the required context is unsatisfiable — pull requests would be blocked while the board shows green.This replaces the inline scanner with the estate-canonical thin wrapper (job id
hypatia→hypatia / Hypatia Neurosymbolic Analysis), pinned to this repo's own standards pinfad242d35291(same SHA its governance wrapper uses), granting exactly what the callee declares. The lockfile manifest is reconciled (gh actions-lock,actions.lockre-parsed,--verifyclean).