Skip to content

Promote develop to main #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ptr727 merged 1 commit into from
Jul 18, 2026
Merged

Promote develop to main #426

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions WORKFLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -587,14 +587,14 @@ determined by NBGV from the checkout state in section 3.*
### 5D. Configuration audit

Follow the read-only audit in [`AUDIT.md`](./AUDIT.md) (section 6). It confirms the listed secrets exist,
the `main`/`develop` rulesets enforce the required merge method + status check + signed commits +
strict-off, and the repository settings (auto-merge, allowed merge methods) are in place, reporting any
drift. A missing or incorrect configuration item is a defect (D10). Secret *values* cannot be read
back, so the audit checks that the names exist, reporting a missing name or a failed query as a defect; the
GitHub App installation is a best-effort check (a precise check needs app-level auth, so it notes rather
than reports a defect). The NuGet.org trusted-publishing
policy (D4.7) lives outside GitHub and cannot be checked by `gh api`, so it sits outside AUDIT.md's drift
report entirely - it is a manual checklist item, verified on NuGet.org (see section 6).
the `main`/`develop` rulesets enforce the required merge method + status check + signed commits, with
"require branches up to date before merging" **off**, and the repository settings (auto-merge, allowed
merge methods) are in place, reporting any drift. A missing or incorrect configuration item is a defect
(D10). Secret *values* cannot be read back, so the audit checks that the names exist, reporting a missing
name or a failed query as a defect; the GitHub App installation is a best-effort check (a precise check
needs app-level auth, so it notes rather than reports a defect). The NuGet.org trusted-publishing policy
(D4.7) lives outside GitHub and cannot be checked by `gh api`, so it sits outside AUDIT.md's drift report
entirely - it is a manual checklist item, verified on NuGet.org (see section 6).

### Assessment

Expand Down