Repository navigation
Establish reviewed GitHub workflow and publication rules - #15
Merged
Merged
Conversation
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
1 participant
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.
Change
Add monthly GitHub Actions and existing branding npm dependency updates, run the existing branding TypeScript check in CI, and add concise repository-specific validation, privacy, and publication instructions. Preserve the existing native CI and its publication-boundary gate.
Verification
Local publication-boundary check and locked branding dependency installation/type check passed. Candidate native build/test and intended-language CodeQL analyses must succeed before merge. Static analysis does not establish live collection on every supported Mac.
Workflow YAML parsed successfully. External checkout Actions are pinned to full commit SHAs verified in the upstream actions/checkout repository. CodeQL is migrated to an advanced workflow that preserves every intended source language. Source extraction/build/analysis runs with read-only token permissions and never uploads; separate jobs upload SARIF without checking out or running repository code. The strict CodeQL results gate requires both analysis and processed uploads to succeed. Candidate-revision analyses and CI must pass before merge.
Scope
Prepared from the refreshed default branch in an isolated worktree; original canonical HEAD, staged/unstaged changes, and untracked files are preserved. Authorization applies only to this infrastructure task.