Skip to content

S0269-dates-drift-check-phase-2: call the org CodeQL reusable - #5

Merged
NSchatz merged 1 commit into
mainfrom
sdd/S0269-dates-drift-check-phase-2
Sep 6, 2026
Merged

NSchatz merged 1 commit into
mainfrom
sdd/S0269-dates-drift-check-phase-2

Conversation

@NSchatz

@NSchatz NSchatz commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Closes the single drift config/drift-manifest.json measures against this repo.

The light baseline's securityWorkflows group requires codeql.yml and
scorecard.yml. This repo carried scorecard.yml, ci.yml and
no-emdash.yml, and was missing codeql.yml alone. Before this change
node config/scripts/drift-check.js printed:

✗ dates: 1 drift(s)
    - [securityWorkflows] .github/workflows/codeql.yml: missing

After it:

✓ dates: matches the light baseline

with no dates row under WORKLIST.

What this is

One new file, .github/workflows/codeql.yml, a thin caller of the org
reusable in cosyte/.github, in the same shape as the scorecard.yml
caller already in this repo. Nothing else is added, modified or deleted.

Two things about the caller worth reading rather than skimming:

  • All three job permissions are required. A called workflow can only
    downgrade its caller's token, never escalate it, so security-events: write, contents: read and actions: read have to be granted here or
    GitHub rejects the workflow at startup, before a step runs.
    .github/CI.md already recorded the same three under the section on
    reusables this repo did not call yet.
  • A published reference, not @main, which departs from scorecard.yml.
    workflows-2026-09-04-f29e9cc83cac resolves to commit
    f29e9cc83cac4bd5fc73a68cefa22f136cd39608 and never names another, so no
    later change in cosyte/.github reaches this repo until this line is
    edited. Both that repo's README and the header of the reusable itself ask
    callers for this form.

One-way door, declared

cosyte/dates is a public repository and this workflow uploads a SARIF
analysis into its Security tab. Deleting the file later stops new analyses;
it does not retract an alert history already written. Accepted, on the same
axis scorecard.yml records for its publish-results: false choice.

Spec: work/specs/S0269-dates-drift-check-phase-2/spec.md in the umbrella.

Closes the one drift config/drift-manifest.json measures against this repo:
the light baseline's securityWorkflows group requires codeql.yml beside
scorecard.yml, and only scorecard.yml was here.

A thin caller, like scorecard.yml, so the analysis stays defined once in
cosyte/.github. The job grants security-events: write, contents: read and
actions: read because a called workflow can only downgrade its caller's
token, and it names the published reference workflows-2026-09-04-f29e9cc83cac
rather than @main so nothing in cosyte/.github reaches this repo until this
line is edited.
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@NSchatz
NSchatz merged commit 8e6e5c7 into main Sep 6, 2026
4 checks passed
@NSchatz
NSchatz deleted the sdd/S0269-dates-drift-check-phase-2 branch October 8, 2026 18:11
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.

2 participants