KofTwentyTwo/gclo
2
0 Fork 0
Code Issues 28 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

Maintainer checklist: repository settings, rulesets, environments, exceptions, and process items for standards compliance #66

New Issue
Open
opened 2026-10-09 14:53:54 +00:00 by KofTwentyTwo · 7 comments
KofTwentyTwo commented 2026-10-09 14:53:54 +00:00 (Migrated from github.com)
Copy link
Copy source

Part of #62 (workstream 4). These are maintainer-only actions (agents must not change settings, K22-AI-10). Tick each as it is done; the order matters because the required-check names change.

Repository settings

  • Merge settings: squash only (disable merge commits and rebase merges); squash title = PR title, squash message = PR body; enable automatically delete head branches (K22-REPO-22).
  • Disable the wiki; set the homepage to the releases page or README (K22-REPO-40/41).
  • Actions permissions: allow GitHub-authored actions, verified creators, and the actions in use (peter-evans/create-pull-request, ossf/scorecard-action, actions/attest-*, astral-sh/setup-uv, docker:// images) (K22-REPO-32).
  • Create the release environment with deployment branches/tags restricted to v*; move any future NUGET_API_KEY / CHOCO_API_KEY / WINGET_TOKEN / DEPS_PAT into it; prefer nuget.org trusted publishing (OIDC) over an API key; use a fine-grained (not classic) token for winget or record an exception (K22-CI-16, REL-11, SEC-03/11).

Rulesets

  • protect-main: add required linear history and required signatures; set require conversation resolution; set require branches to be up to date; allowed merge methods = squash; required checks = pr / title, pr / dco, pr / dependency-review, security / secrets, security / sca, security / workflows, codeql / analyze (csharp), codeql / analyze (actions), Build and test (x64), Format (style gate) (then ci / build-test, ci / format once the cleanup PR renames them). Keep bypass actors empty (K22-REPO-20, CI-01).
  • protect-release-tags: add the creation rule; add exactly one bypass actor, Repository admin (K22-REPO-21).
  • Retire dev: delete the protect-dev ruleset and the dev branch once the standards PRs are on main (K22-SDLC-10).
  • After the ruleset lists the new contexts, merge the "ci: remove superseded gates" follow-up PR.

Organization and standards repository

  • Create the account-wide KofTwentyTwo/.github repository with CODE_OF_CONDUCT.md (or keep the copy this repo gains) (K22-REPO-10).
  • Merge the exception-register PR in KofTwentyTwo/standards: libgit2 GPL-2.0 WITH linking exception and Microsoft SDK license terms (K22-DEP-02); in-repo release workflow until the shared release workflow exists (K22-CI-30, REL-04); update EX-0002's "current state" (gclo now ships SHA256SUMS and attestations).
  • Add the allow-dependencies-licenses input to the standards' pr.yml (packages whose nuspec names a license file) and re-pin gclo's callers.

Process and account

  • Complete the v1.0.1 release-checklist issue (K22-REL-12) and attach the conformance output (K22-SDLC-33).
  • Open the annual access-review issue in the standards repository (K22-SEC-04); phishing-resistant MFA, weekly off-GitHub backups, offline recovery codes, named successor (K22-SEC-01, 60, 61, 62).
  • Pin the Claude plugin versions in .claude/settings.json (K22-AI-12).
Part of #62 (workstream 4). These are maintainer-only actions (agents must not change settings, K22-AI-10). Tick each as it is done; the order matters because the required-check names change. ## Repository settings - [ ] Merge settings: squash only (disable merge commits and rebase merges); squash title = **PR title**, squash message = **PR body**; enable *automatically delete head branches* (K22-REPO-22). - [ ] Disable the wiki; set the homepage to the releases page or README (K22-REPO-40/41). - [ ] Actions permissions: allow GitHub-authored actions, verified creators, and the actions in use (`peter-evans/create-pull-request`, `ossf/scorecard-action`, `actions/attest-*`, `astral-sh/setup-uv`, docker:// images) (K22-REPO-32). - [ ] Create the `release` environment with deployment branches/tags restricted to `v*`; move any future `NUGET_API_KEY` / `CHOCO_API_KEY` / `WINGET_TOKEN` / `DEPS_PAT` into it; prefer nuget.org trusted publishing (OIDC) over an API key; use a fine-grained (not classic) token for winget or record an exception (K22-CI-16, REL-11, SEC-03/11). ## Rulesets - [ ] `protect-main`: add **required linear history** and **required signatures**; set *require conversation resolution*; set *require branches to be up to date*; allowed merge methods = squash; required checks = `pr / title`, `pr / dco`, `pr / dependency-review`, `security / secrets`, `security / sca`, `security / workflows`, `codeql / analyze (csharp)`, `codeql / analyze (actions)`, `Build and test (x64)`, `Format (style gate)` (then `ci / build-test`, `ci / format` once the cleanup PR renames them). Keep bypass actors empty (K22-REPO-20, CI-01). - [ ] `protect-release-tags`: add the **creation** rule; add exactly one bypass actor, *Repository admin* (K22-REPO-21). - [ ] Retire `dev`: delete the `protect-dev` ruleset and the `dev` branch once the standards PRs are on `main` (K22-SDLC-10). - [ ] After the ruleset lists the new contexts, merge the "ci: remove superseded gates" follow-up PR. ## Organization and standards repository - [ ] Create the account-wide `KofTwentyTwo/.github` repository with `CODE_OF_CONDUCT.md` (or keep the copy this repo gains) (K22-REPO-10). - [ ] Merge the exception-register PR in `KofTwentyTwo/standards`: libgit2 `GPL-2.0 WITH linking exception` and Microsoft SDK license terms (K22-DEP-02); in-repo release workflow until the shared release workflow exists (K22-CI-30, REL-04); update EX-0002's "current state" (gclo now ships `SHA256SUMS` and attestations). - [ ] Add the `allow-dependencies-licenses` input to the standards' `pr.yml` (packages whose nuspec names a license file) and re-pin gclo's callers. ## Process and account - [ ] Complete the v1.0.1 release-checklist issue (K22-REL-12) and attach the conformance output (K22-SDLC-33). - [ ] Open the annual access-review issue in the standards repository (K22-SEC-04); phishing-resistant MFA, weekly off-GitHub backups, offline recovery codes, named successor (K22-SEC-01, 60, 61, 62). - [ ] Pin the Claude plugin versions in `.claude/settings.json` (K22-AI-12).
KofTwentyTwo commented 2026-10-09 15:41:46 +00:00 (Migrated from github.com)
Copy link
Copy source

Status 2026-10-09 (agent)

Everything file-side is in pull requests, stacked so each diff stays reviewable; merge in this order (squash):

  1. #68 ci: adopt the standards' gates (all checks green).
  2. #69 docs: governance files, ADRs, threat model (green).
  3. #70 style: Kingsrook layout + quality gate — every check green except pr / dependency-review, which fails only because central package management makes the dependency graph re-evaluate LibGit2Sharp, Microsoft.WindowsAppSDK, Microsoft.Windows.SDK.BuildTools (file-licensed, reported as NOASSERTION). The fix is the allow-dependencies-licenses input proposed in KofTwentyTwo/standards PR (see below); until that is merged and gclo re-pins, the old Dependency review check (which exempts them) is the one that passes.
  4. #71 (draft) ci: retire the superseded gates — only after the ruleset edit described in the PR.

Then: add the squash commit of #70 to .git-blame-ignore-revs (git log --format=%H -1 --grep="style: adopt the Kingsrook"), one tiny chore: PR.

Standards repository

  • Merge KofTwentyTwo/standards PR "fix(pr): exempt file-licensed packages, accept the security type, and keep the DCO check robust" (EX-0003 licenses, EX-0004 in-repo release workflow, allow-dependencies-licenses input, DCO parsing fix, analyzer settings conflict). Then re-pin gclo's three callers (pr-gates.yml, security.yml, codeql.yml) to the merged SHA and set with: allow-dependencies-licenses: pkg:nuget/LibGit2Sharp, pkg:nuget/Microsoft.WindowsAppSDK, pkg:nuget/Microsoft.Windows.SDK.BuildTools on pr-gates.yml (Dependabot will also offer the re-pin).

Still maintainer-only (unchanged from the checklist above)

Merge settings (squash only, PR title/body, auto-delete), protect-main rules and required contexts, protect-release-tags creation rule + admin bypass, wiki off, homepage, allowed actions, release environment for secrets, org .github / CoC, retiring dev + protect-dev, the v1.0.1 release checklist (#67) with the conformance output, the annual access-review issue, MFA/backup/recovery attestations, plugin pins in .claude/settings.json.

Verified by the conformance checker today (tools/Test-RepoConformance.ps1 -Repository KofTwentyTwo/gclo -LocalPath . on the stacked branches)

PASS: REPO-01/02/04/05/06/07/08/09/11/30/31/42, CI-02/03 (review), CI-10..15, 17, 18, 20..24. Remaining FAIL/WARN are all settings or exceptions: REPO-20/21/22/40 (rulesets, merge settings, wiki), REPO-10/32/41 (org .github, allowed actions, homepage), CI-01 (required contexts), CI-30 (EX-0004 once merged), REPO-03 clears with #70 (LF).

## Status 2026-10-09 (agent) Everything file-side is in pull requests, stacked so each diff stays reviewable; merge in this order (squash): 1. **#68** `ci: adopt the standards' gates` (all checks green). 2. **#69** `docs: governance files, ADRs, threat model` (green). 3. **#70** `style: Kingsrook layout + quality gate` — every check green except `pr / dependency-review`, which fails only because central package management makes the dependency graph re-evaluate `LibGit2Sharp`, `Microsoft.WindowsAppSDK`, `Microsoft.Windows.SDK.BuildTools` (file-licensed, reported as NOASSERTION). The fix is the `allow-dependencies-licenses` input proposed in **KofTwentyTwo/standards PR** (see below); until that is merged and gclo re-pins, the old `Dependency review` check (which exempts them) is the one that passes. 4. **#71** (draft) `ci: retire the superseded gates` — only after the ruleset edit described in the PR. Then: add the squash commit of #70 to `.git-blame-ignore-revs` (`git log --format=%H -1 --grep="style: adopt the Kingsrook"`), one tiny `chore:` PR. ### Standards repository - Merge **KofTwentyTwo/standards** PR "fix(pr): exempt file-licensed packages, accept the security type, and keep the DCO check robust" (EX-0003 licenses, EX-0004 in-repo release workflow, `allow-dependencies-licenses` input, DCO parsing fix, analyzer settings conflict). Then re-pin gclo's three callers (`pr-gates.yml`, `security.yml`, `codeql.yml`) to the merged SHA and set `with: allow-dependencies-licenses: pkg:nuget/LibGit2Sharp, pkg:nuget/Microsoft.WindowsAppSDK, pkg:nuget/Microsoft.Windows.SDK.BuildTools` on `pr-gates.yml` (Dependabot will also offer the re-pin). ### Still maintainer-only (unchanged from the checklist above) Merge settings (squash only, PR title/body, auto-delete), `protect-main` rules and required contexts, `protect-release-tags` creation rule + admin bypass, wiki off, homepage, allowed actions, `release` environment for secrets, org `.github` / CoC, retiring `dev` + `protect-dev`, the v1.0.1 release checklist (#67) with the conformance output, the annual access-review issue, MFA/backup/recovery attestations, plugin pins in `.claude/settings.json`. ### Verified by the conformance checker today (`tools/Test-RepoConformance.ps1 -Repository KofTwentyTwo/gclo -LocalPath .` on the stacked branches) PASS: REPO-01/02/04/05/06/07/08/09/11/30/31/42, CI-02/03 (review), CI-10..15, 17, 18, 20..24. Remaining FAIL/WARN are all settings or exceptions: REPO-20/21/22/40 (rulesets, merge settings, wiki), REPO-10/32/41 (org .github, allowed actions, homepage), CI-01 (required contexts), CI-30 (EX-0004 once merged), REPO-03 clears with #70 (LF).
KofTwentyTwo commented 2026-10-09 15:43:49 +00:00 (Migrated from github.com)
Copy link
Copy source

Standards pull request: https://github.com/KofTwentyTwo/standards/pull/4 (merge it first, then re-pin gclo's three callers and add the allow-dependencies-licenses input on pr-gates.yml).

Standards pull request: https://github.com/KofTwentyTwo/standards/pull/4 (merge it first, then re-pin gclo's three callers and add the `allow-dependencies-licenses` input on `pr-gates.yml`).
KofTwentyTwo commented 2026-10-09 16:01:28 +00:00 (Migrated from github.com)
Copy link
Copy source

Status update (2026-10-09, afternoon)

Done by the agent

  • standards#4 merged (squash, ae174f5): allow-dependencies-licenses input, DCO fix, security title type, EX-0003/EX-0004, PSScriptAnalyzer CheckOperator off, plus two follow-on fixes found while making its own docs gate pass: a .markdownlint-cli2.yaml (MD013/MD033/MD036/MD041 off, remaining findings fixed in place) and a working lychee link check (the binary was never at ./lychee; it is now extracted under RUNNER_TEMP, with lychee.toml excluding template placeholder links). The docs gate had been failing on standards main itself.
  • gclo callers re-pinned to ae174f54959ba4297f2ae174356c4481918fdf44 on ci/standards-gates (#68), with the license exemption input for LibGit2Sharp, Microsoft.WindowsAppSDK and Microsoft.Windows.SDK.BuildTools. #68 is green on all 15 checks and CLEAN/MERGEABLE.
  • Rulesets applied via API:
    • protect-main (18480002): added required_linear_history and required_signatures; required_review_thread_resolution: true; allowed_merge_methods: [squash]; strict_required_status_checks_policy: true. Contexts are still the old four (Build and test (x64), Format (style gate), Dependency review, CodeQL) so #68–#70 can merge.
    • protect-release-tags (18484691): added the creation rule and a bypass for the repository admin role (RepositoryRole 5, always).

Blocked: needs the maintainer (the agent's tooling refuses these two actions)

  1. Repository settings (one call): 
    gh api -X PATCH repos/KofTwentyTwo/gclo -f allow_merge_commit=false -f allow_rebase_merge=false -f allow_squash_merge=true -f delete_branch_on_merge=true -f squash_merge_commit_title=PR_TITLE -f squash_merge_commit_message=PR_BODY -f has_wiki=false -f homepage=https://github.com/KofTwentyTwo/gclo/releases/latest
    Also gh pr edit 48 --base main (stale macOS draft; needed before dev can go).
  2. Merge the stack (squash, in order; strict checks mean each stacked branch must be rebased onto the new main after the previous merge): 
    gh pr merge 68 --squash
git fetch origin && git checkout docs/standards-governance && git rebase --onto origin/main origin/ci/standards-gates && git push --force-with-lease && gh pr edit 69 --base main
# wait for green, then
gh pr merge 69 --squash
git checkout style/kingsrook-layout && git rebase --onto origin/main origin/docs/standards-governance && git push --force-with-lease && gh pr edit 70 --base main
gh pr merge 70 --squash
    Then switch protect-main required contexts to pr / title, pr / dco, pr / dependency-review, security / secrets, security / sca, security / workflows, codeql / analyze (csharp), codeql / analyze (actions), mark #71 ready, rebase it the same way, merge it, and add ci / build-test, ci / format, ci / ui-tests to the contexts.
  3. After #70 merges: a chore: ignore the layout commit in git blame PR adding .git-blame-ignore-revs with #70's squash SHA.
  4. Delete dev and the protect-dev ruleset (18480003) once #48 targets main.

Items 1–2 are the only things between the repository and the v1.0.1 tag (#67); the agent cannot perform them.

## Status update (2026-10-09, afternoon) ### Done by the agent - **standards#4 merged** (squash, `ae174f5`): `allow-dependencies-licenses` input, DCO fix, `security` title type, EX-0003/EX-0004, PSScriptAnalyzer `CheckOperator` off, plus two follow-on fixes found while making its own `docs` gate pass: a `.markdownlint-cli2.yaml` (MD013/MD033/MD036/MD041 off, remaining findings fixed in place) and a working lychee link check (the binary was never at `./lychee`; it is now extracted under `RUNNER_TEMP`, with `lychee.toml` excluding template placeholder links). The `docs` gate had been failing on standards `main` itself. - **gclo callers re-pinned** to `ae174f54959ba4297f2ae174356c4481918fdf44` on `ci/standards-gates` (#68), with the license exemption input for LibGit2Sharp, Microsoft.WindowsAppSDK and Microsoft.Windows.SDK.BuildTools. **#68 is green on all 15 checks and `CLEAN`/`MERGEABLE`.** - **Rulesets applied via API:** - `protect-main` (18480002): added `required_linear_history` and `required_signatures`; `required_review_thread_resolution: true`; `allowed_merge_methods: [squash]`; `strict_required_status_checks_policy: true`. Contexts are still the old four (`Build and test (x64)`, `Format (style gate)`, `Dependency review`, `CodeQL`) so #68–#70 can merge. - `protect-release-tags` (18484691): added the `creation` rule and a bypass for the repository admin role (`RepositoryRole` 5, always). ### Blocked: needs the maintainer (the agent's tooling refuses these two actions) 1. **Repository settings** (one call): ```sh gh api -X PATCH repos/KofTwentyTwo/gclo -f allow_merge_commit=false -f allow_rebase_merge=false -f allow_squash_merge=true -f delete_branch_on_merge=true -f squash_merge_commit_title=PR_TITLE -f squash_merge_commit_message=PR_BODY -f has_wiki=false -f homepage=https://github.com/KofTwentyTwo/gclo/releases/latest ``` Also `gh pr edit 48 --base main` (stale macOS draft; needed before `dev` can go). 2. **Merge the stack** (squash, in order; strict checks mean each stacked branch must be rebased onto the new `main` after the previous merge): ```sh gh pr merge 68 --squash git fetch origin && git checkout docs/standards-governance && git rebase --onto origin/main origin/ci/standards-gates && git push --force-with-lease && gh pr edit 69 --base main # wait for green, then gh pr merge 69 --squash git checkout style/kingsrook-layout && git rebase --onto origin/main origin/docs/standards-governance && git push --force-with-lease && gh pr edit 70 --base main gh pr merge 70 --squash ``` Then switch `protect-main` required contexts to `pr / title`, `pr / dco`, `pr / dependency-review`, `security / secrets`, `security / sca`, `security / workflows`, `codeql / analyze (csharp)`, `codeql / analyze (actions)`, mark #71 ready, rebase it the same way, merge it, and add `ci / build-test`, `ci / format`, `ci / ui-tests` to the contexts. 3. After #70 merges: a `chore: ignore the layout commit in git blame` PR adding `.git-blame-ignore-revs` with #70's squash SHA. 4. Delete `dev` and the `protect-dev` ruleset (18480003) once #48 targets `main`. Items 1–2 are the only things between the repository and the `v1.0.1` tag (#67); the agent cannot perform them.
KofTwentyTwo commented 2026-10-09 16:19:05 +00:00 (Migrated from github.com)
Copy link
Copy source

Update: after rebasing the stack onto the re-pinned #68 and fixing an intermittent PSScriptAnalyzer crash in the format job (#70 now runs it one script per call), #68, #69, #70 and #71 are all green and CLEAN. #70's pr / dependency-review passes with the license exemption. Only the maintainer steps above (settings PATCH, merges in order with a rebase onto main between each, context switch) remain.

Update: after rebasing the stack onto the re-pinned #68 and fixing an intermittent PSScriptAnalyzer crash in the format job (#70 now runs it one script per call), **#68, #69, #70 and #71 are all green and `CLEAN`**. #70's `pr / dependency-review` passes with the license exemption. Only the maintainer steps above (settings PATCH, merges in order with a rebase onto `main` between each, context switch) remain.
KofTwentyTwo commented 2026-10-09 19:47:38 +00:00 (Migrated from github.com)
Copy link
Copy source

Update 16:50 UTC: #68, #69, #70 merged (squash: a562acd, 1ff4398, 50b3c13). Repository settings applied (squash-only, PR_TITLE/PR_BODY, delete branch on merge, wiki off, homepage). protect-main required contexts switched to the final set: pr / title, pr / dco, pr / dependency-review, security / secrets, security / sca, security / workflows, codeql / analyze (csharp), codeql / analyze (actions), build-test, format, ui-tests (note: plain job names, not ci / …; CONTRIBUTING's gate table needs that correction). #48 retargeted to main. #71 rebased onto main, ready, all 14 checks pass; #73 (.git-blame-ignore-revs, Closes #72) opened.

Remaining, in order: gh pr merge 71 --squash → rebase chore/blame-ignore-revs onto main and merge #73 → delete dev and ruleset 18480003 → #67 checklist → tag v1.0.1.

Update 16:50 UTC: **#68, #69, #70 merged** (squash: `a562acd`, `1ff4398`, `50b3c13`). Repository settings applied (squash-only, PR_TITLE/PR_BODY, delete branch on merge, wiki off, homepage). `protect-main` required contexts switched to the final set: `pr / title`, `pr / dco`, `pr / dependency-review`, `security / secrets`, `security / sca`, `security / workflows`, `codeql / analyze (csharp)`, `codeql / analyze (actions)`, `build-test`, `format`, `ui-tests` (note: plain job names, not `ci / …`; CONTRIBUTING's gate table needs that correction). #48 retargeted to `main`. #71 rebased onto main, ready, **all 14 checks pass**; #73 (`.git-blame-ignore-revs`, Closes #72) opened. Remaining, in order: `gh pr merge 71 --squash` → rebase `chore/blame-ignore-revs` onto main and merge #73 → delete `dev` and ruleset 18480003 → #67 checklist → tag `v1.0.1`.
KofTwentyTwo commented 2026-10-11 13:17:12 +00:00 (Migrated from github.com)
Copy link
Copy source

Status 2026-10-11 (agent, on the owner's instruction):

  • K22-REPO-10: created the account-wide https://github.com/KofTwentyTwo/.github (CODE_OF_CONDUCT.md, SUPPORT.md, profile README, MIT). Issue/PR templates stay per repository.
  • K22-REPO-32: applied allowed_actions=selected on this repository (GitHub-authored + verified creators + KofTwentyTwo/, peter-evans/create-pull-request@, azure/login@, azure/artifact-signing-action@, ossf/scorecard-action@, astral-sh/setup-uv@, googleapis/release-please-action@*). ci, codeql and scorecard re-ran green. The security workflow fails at startup under this policy: the shared KofTwentyTwo/standards security workflow runs gitleaks and trivy as docker:// container steps, which the selected-actions allow list cannot express. Owner decision needed: either set Actions permissions back to 'Allow all actions' until the shared workflow switches to GitHub-hosted actions for those two scanners, or keep the policy and accept the security gate being red.
  • winget: first manifests submitted as microsoft/winget-pkgs#450621; WINGET_PACKAGE_ID=KofTwentyTwo.gclo and release-env WINGET_TOKEN are set (token source: the existing 1Password GITHUB_TOKEN item, classic, scopes unverified; a fine-grained token is still the standards' preference).
Status 2026-10-11 (agent, on the owner's instruction): - K22-REPO-10: created the account-wide https://github.com/KofTwentyTwo/.github (CODE_OF_CONDUCT.md, SUPPORT.md, profile README, MIT). Issue/PR templates stay per repository. - K22-REPO-32: applied allowed_actions=selected on this repository (GitHub-authored + verified creators + KofTwentyTwo/*, peter-evans/create-pull-request@*, azure/login@*, azure/artifact-signing-action@*, ossf/scorecard-action@*, astral-sh/setup-uv@*, googleapis/release-please-action@*). ci, codeql and scorecard re-ran green. The **security** workflow fails at startup under this policy: the shared KofTwentyTwo/standards security workflow runs gitleaks and trivy as docker:// container steps, which the selected-actions allow list cannot express. Owner decision needed: either set Actions permissions back to 'Allow all actions' until the shared workflow switches to GitHub-hosted actions for those two scanners, or keep the policy and accept the security gate being red. - winget: first manifests submitted as microsoft/winget-pkgs#450621; WINGET_PACKAGE_ID=KofTwentyTwo.gclo and release-env WINGET_TOKEN are set (token source: the existing 1Password GITHUB_TOKEN item, classic, scopes unverified; a fine-grained token is still the standards' preference).
KofTwentyTwo commented 2026-10-11 13:30:23 +00:00 (Migrated from github.com)
Copy link
Copy source

Owner set Actions permissions back to 'Allow all actions'; the security workflow re-ran green on main. K22-REPO-32 stays open on this repository until https://github.com/KofTwentyTwo/standards/issues/35 lands in the shared security workflow.

Owner set Actions permissions back to 'Allow all actions'; the security workflow re-ran green on main. K22-REPO-32 stays open on this repository until https://github.com/KofTwentyTwo/standards/issues/35 lands in the shared security workflow.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
.NET
Pull requests that update .NET code
 bug
Something isn't working
 deferred
Agreed follow-up, not scheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on an action only the owner can take
 priority
Owner-flagged: work this first
 quality
Standards, simplicity, enforcement
 question
Further information is requested
 refactor
Restructuring without behavior change
 release
Release pipeline / distribution
 wontfix
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#66