Skip to content

Document generated permissions and preserve author comments - #75615

Merged
pelikhan merged 7 commits into
mainfrom
copilot/fix-undocumented-permissions
Nov 7, 2026
Merged

pelikhan merged 7 commits into
mainfrom
copilot/fix-undocumented-permissions

Conversation

Copilot AI commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Compiled workflows lose author permission comments and omit scope-level explanations required by zizmor’s pedantic undocumented-permissions check.

  • Scope explanations: Add reasons for permissions beyond contents: read across agentic, maintenance, central-command, work-queue, and auto-update workflows.
  • Comment preservation: Retain block and scope comments on agent, custom, and safe-output jobs, including permission overrides and normalized safe-job IDs.
  • Regression coverage: Check comment placement and unchanged permission values and script contents.

Generated permissions now include explanations while retaining author-provided reasons:

permissions:
  contents: read
  issues: write # Create or update issues and comments.
  checks: write # Publish the report check

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix omission of permission comments in lock files Document generated permissions and preserve author comments Nov 7, 2026
Copilot AI requested a review from pelikhan November 7, 2026 06:06
@pelikhan
pelikhan marked this pull request as ready for review November 7, 2026 14:04
Copilot AI dynamic review requested due to automatic review settings November 7, 2026 14:04
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

✅ Test Quality Sentinel completed test quality analysis.

Test Quality Sentinel

Outcome: reported_no_action

The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible.

Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.

Generated from Test Quality Sentinel · routed: gpt56 max · ~1 AIC · ⌖ ~2 AIC · ⊞ 6.3K · ◷

🧪 Test quality analysis by Test Quality Sentinel

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

✅ Ponytail Reviewer completed successfully!

Warning

Threat detection engine error

Threat detection could not complete its analysis due to a tooling error. This is not a security finding.

What happened

The threat detection results could not be parsed.

Review the workflow run logs to troubleshoot the error.

Generated by Ponytail Reviewer for #75615

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

❌ Design Decision Gate 🏗️ failed to deliver outputs during design decision gate check.

🏗️ ADR gate enforced by Design Decision Gate 🏗️

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

✅ PR Specification Reviewer completed successfully!

PR Specification Reviewer

Outcome: reported_no_action

The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible.

Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.

Generated from PR Specification Reviewer · gpt56 · ~3 AIC · ⌖ ~1 AIC · ⊞ 1.6K · ◷

Generated by PR Specification Reviewer for #75615

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

✅ PR Code Quality Reviewer completed the code quality review.

🔎 Code quality review by PR Code Quality Reviewer

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅

Warning

Threat detection engine error

Threat detection could not complete its analysis due to a tooling error. This is not a security finding.

What happened

The threat detection results could not be parsed.

Review the workflow run logs to troubleshoot the error.

🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Warning

The push_to_pull_request_branch operation failed: Cannot verify branch protection rules for "copilot/fix-undocumented-permissions": Resource not accessible by integration - https://docs.github.com/rest/branches/branch-protection\#get-branch-protection. Reading classic branch protection requires a GitHub App installation token or fine-grained PAT with Administration: read repository permission; GITHUB_TOKEN cannot provide this permission. Push blocked to prevent accidental writes to protected branches.. The code changes were not applied.

🏗️ Design Decision Gate — ADR Required

This PR makes significant changes to core workflow-compilation logic (488 new lines in pkg/workflow, above the 100-line threshold) but does not have a linked Architecture Decision Record (ADR).

📄 Draft ADR committed: docs/adr/75615-preserve-generated-permission-comments.md — review and complete it before merging.

🔒 This PR cannot merge until an ADR is linked in the PR body.

📋 Evidence and what to do next

The gate used the following PR evidence:

  • pkg/workflow/compiler_permission_comments.go adds a centralized YAML-AST-guided pass for preserving source comments and generating scope explanations.
  • pkg/workflow/compiler_yaml.go and the auxiliary workflow generators apply that pass to compiled output.
  • The PR body and linked issue v1.0.1 lock files still omit permission comments (zizmor pedantic undocumented-permissions) #75581 identify zizmor pedantic undocumented-permissions findings and loss of author-provided permission comments as the motivating problem.
  1. Review the draft ADR committed to your branch.

  2. Complete the missing sections — add context the AI could not infer, refine the decision rationale, and confirm the alternatives and trade-offs.

  3. Commit the finalized ADR to docs/adr/.

  4. Reference the ADR in this PR body by adding:

    ADR: ADR-75615: Preserve and Document Generated Permission Comments (link unavailable: invalid HTTPS URL)

Once the ADR is linked in the PR body, this gate will re-run and verify that the implementation matches the decision.

❓ Why ADRs Matter

ADRs create a searchable, permanent record of why the codebase looks the way it does, including the alternatives and trade-offs future contributors need to understand.

📋 Michael Nygard ADR Format Reference

An ADR must contain these four sections to be considered complete:

  • Context — What is the problem? What forces are at play?
  • Decision — What was decided, and why?
  • Alternatives Considered — What else could have been done?
  • Consequences — What are the trade-offs, both positive and negative?

All ADRs are stored in docs/adr/ and use a four-or-more-digit sequence based on the PR number.

🏗️ ADR gate enforced by Design Decision Gate 🏗️ · pi · routed: gpt56 max · ~3 AIC · ⌖ ~2 AIC · ⊞ 7.7K · ◷
Comment /review to run again

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warning

Threat detection engine error

Threat detection could not complete its analysis due to a tooling error. This is not a security finding.

What happened

The threat detection results could not be parsed.

Review the workflow run logs to troubleshoot the error.

What this change does: This change adds a YAML-node pass that copies author permission comments onto generated permissions and fills missing scope reasons. It also applies that pass to auxiliary workflow generators and adds regression tests for comments and unchanged values.

Should fix:

  1. Remove the stranded generated-job name table (pkg/workflow/compiler_job_annotations.go:L47)

    • What this is: The old branch that read generatedJobNames was removed.
    • Problem: A repository-wide search now finds only notify_comment_failed_jobs_test.go:144; the 23-entry map and assertion no longer affect compilation but remain as dead state.
    • Fix: Delete generatedJobNames and the assertion that only protects it.
    • If we skip it: Future readers will assume the table still controls compiler behavior and will maintain code that cannot run.

Verdict: fix 1 first.
Lean: -24 lines possible.

Generated by ✂️ Ponytail Reviewer for #75615 · codex · routed: gpt56 max · ~7 AIC · ⌖ ~1 AIC · ⊞ 118
Comment /ponytail to run again

}
_, generated := generatedJobNames[id]
if job.PermissionsComment == "" && (generated || len(sourceComments[id]) == 0) {
if job.PermissionsComment == "" {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lean: Deleting the generated-name branch leaves generatedJobNames with no production callers (only notify_comment_failed_jobs_test.go:144); remove the 23-line map and that assertion, or this dead state will keep looking like compiler behavior.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the unused generatedJobNames map and its sole remaining assertion in df3f6b4.

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Comment Memory

Peek at saved memory (pr-code-quality-reviewer)
reviewed_at: 2026-11-07T14:07:27Z
review_event: REQUEST_CHANGES
top_themes: [permission comment preservation]
files_reviewed: [pkg/workflow/compiler_permission_comments.go, pkg/workflow/compiler_yaml.go, pkg/workflow/compiler_job_annotations.go, pkg/workflow/compiler_job_annotations_test.go, pkg/workflow/compiler_permission_comments_test.go]
comment_count: 1

Note

This comment is managed by comment memory.

Expand the saved memory block to view or edit the persistent context for this thread.
Edit only the text inside the backtick fences; workflow metadata and the footer are regenerated automatically.

Learn more about comment memory

🔎 Code quality review by PR Code Quality Reviewer · copilot · gpt50 · ~5 AIC · ⌖ ~2 AIC · ⊞ 1.6K · ◷
Comment /review to run again

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found one correctness issue blocking merge: frontmatter-level permission comments are not passed into the top-level generated permissions block, so the new preservation behavior drops those author comments (and the added regression test should fail). See the inline comment on compiler_permission_comments.go:227.

The specialist pass completed; its other suggestions were not actionable or did not meet the review threshold.

🔎 Code quality review by PR Code Quality Reviewer · copilot · gpt50 · ~5 AIC · ⌖ ~2 AIC · ⊞ 1.6K
Comment /review to run again

edits := permissionCommentEdits{
lines: strings.Split(content, "\n"), before: make(map[int][]string), after: make(map[int][]string),
}
edits.documentJob(permissionCommentEntry(document.Content[0], "permissions"), permissionCommentSource{}) //nolint:uncheckedsliceindex // The empty-document guard above ensures a root exists.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The generated top-level permissions block never receives the source comment mapping, so author comments on frontmatter-level permissions are silently dropped. This contradicts the preservation goal and the added TestDocumentPermissionComments expectation for # Agent permissions / # Agent context. Pass sources[string(constants.AgentJobName)] (or equivalent) here so root permission comments are copied as well.

💡 Why this matters

permissionCommentSources explicitly stores the root permissions comments under the agent job key, but this call supplies an empty source. As a result, the root block is only auto-documented and never inherits author comments, while job-level comments work.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Root permission comments are now mapped to the generated agent permissions block in df3f6b4.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Reparsing frontmatter without non-breaking-space normalization can break previously accepted workflows, while permission comments are still lost for built-in job aliases and all: read.

3 open issues
What changed in this PR

This PR updates gh-aw’s workflow compiler to document generated permission scopes and preserve author-written permission comments, addressing the zizmor reporting gap in #75581.

Changes:

  • Add scope explanations across primary and auxiliary workflow generators.
  • Replace text-based comment collection with YAML-aware preservation.
  • Add regression coverage for comment placement, permission values, and unchanged scripts.
File Description
pkg/​workflow/​work_queue_event_workflow.go Document work-queue workflow permissions.
pkg/​workflow/​side_repo_maintenance.go Document side-repository maintenance permissions.
pkg/​workflow/​maintenance_workflow_yaml.go Document maintenance workflow permissions.
pkg/​workflow/​compiler_yaml.go Apply permission comments during compilation.
pkg/​workflow/​compiler_permission_comments.go Preserve author comments and generate scope explanations.
pkg/​workflow/​compiler_permission_comments_test.go Test preservation, scope explanations, and unchanged YAML semantics.
pkg/​workflow/​compiler_job_annotations.go Remove the previous text-based comment collector.
pkg/​workflow/​compiler_job_annotations_test.go Update assertions for preserved comment placement.
pkg/​workflow/​central_slash_command_workflow.go Document central-command workflow permissions.
pkg/​workflow/​auto_update_workflow.go Document auto-update workflow permissions.

Review effort: Balanced (auto)

func permissionCommentSources(frontmatter string) (map[string]permissionCommentSource, error) {
result := make(map[string]permissionCommentSource)
var document yaml.Node
if err := yaml.Unmarshal([]byte(frontmatter), &document); err != nil {
for i := 0; i+1 < len(jobs.Content); i += 2 {
source := permissionCommentEntry(jobs.Content[i+1], "permissions") //nolint:uncheckedsliceindex // The loop bounds both members of this mapping entry.
if source.key != nil {
id := jobs.Content[i].Value //nolint:uncheckedsliceindex // The loop bounds both members of this mapping entry.
Comment on lines +165 to +167
for current := &source; current != nil; current = current.inherited {
e.copyComments(perms, *current)
}

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warning

Threat detection engine error

Threat detection could not complete its analysis due to a tooling error. This is not a security finding.

What happened

The threat detection results could not be parsed.

Review the workflow run logs to troubleshoot the error.

Skills-Based Review 🧠

Applied /diagnosing-bugs and /codebase-design. Requesting changes because the new permission-comment pass makes compilation fail on output that previously compiled.

📋 Key Themes & Highlights

Key Themes

  • Regression (blocking): documentPermissionComments parses the whole compiled workflow with yaml.Unmarshal and aborts on error. Two inputs now fail: on: "push" produces a bare push line, and a draft: false pull_request test produces an unquoted GH_AW_CURRENT_WORKFLOW_REF value. Roughly 8 tests fail, including TestPullRequestDraftFilter, TestASCIILogoAlignment, TestOutputCommentJobGeneration, and the WASM golden tests. With this step disabled, those pass.
  • Lock files out of date: Compiled output changes (new reason comments), but no .lock.yml files were regenerated. Run make recompile (AGENTS.md rule 4). ab-testing-advisor.lock.yml shows drift on recompile.
  • Dead code: generatedJobNames in compiler_job_annotations.go is now only referenced by a test. Remove it, or the test, if it is no longer needed.

Positive Highlights

  • ✅ sourceJobPermissionComments has no remaining callers, so the removal is clean.
  • ✅ The reason-text table in permissionScopeReason is easy to extend, and contents: read is skipped deliberately.

Caveats

  • Environmental failures in this sandbox (mktemp permission denied, inherited GITHUB_TOKEN, and a clock-dependent enclave-expiry assertion) are not caused by this PR. No clean baseline could be built because git fetches of the parent commit fail.

@copilot please address the review comments above.

🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · copilot · routed: haiku55 xhigh · ~7 AIC · ⌖ ~1 AIC · ⊞ 5.4K
Comment /matt to run again

return "", err
}
var document yaml.Node
if err := yaml.Unmarshal([]byte(content), &document); err != nil {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[/diagnosing-bugs] This new parse turns previously-compiling output into a hard compile error. documentPermissionComments now runs yaml.Unmarshal over the entire generated workflow and returns an error on failure. Any existing rendering quirk now breaks gh aw compile. Examples: the unquoted GH_AW_CURRENT_WORKFLOW_REF line when the test workflow name contains : , and the bare push line produced by on: "push". Disabling this call makes TestPullRequestDraftFilter, TestASCIILogoAlignment, TestOutputCommentJobGeneration, and the WASM golden tests pass again.

💡 Suggested fix

Do not make a best-effort annotation pass fatal. On parse failure, return content, nil and log at debug level, or skip annotations when the document is not valid YAML. Add a regression test that compiles an on: "push" workflow and a pull_request workflow with draft: false and asserts success.

@copilot please address this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Permission-comment parsing failures now leave generated YAML unchanged instead of failing compilation in df3f6b4. The reported compile regressions pass locally.

Comment thread pkg/workflow/compiler_yaml.go Outdated
if err != nil {
return "", nil, nil, fmt.Errorf("runner temp safety rewriting could not complete; ensure generated run/script steps are valid shell or JavaScript commands: %w", err)
}
yamlContent, err = documentPermissionComments(yamlContent, data.FrontmatterYAML)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[/codebase-design] This call site applies the new post-processing to every compiled workflow, so any failure in it aborts the whole compile. Keep the annotation pass non-fatal here, or make it a separate step that runs after validation succeeds.

@copilot please address this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The annotation pass now logs errors and continues compilation without changing the generated YAML in df3f6b4.

@gh-aw-bot

Copy link
Copy Markdown
Collaborator

@copilot

Copilot assignment requested for the following outstanding work:

  1. Update this branch with the latest main using make merge-main, resolving any conflicts and preserving the intended changes.
  2. Review (pkg/workflow/compiler_job_annotations.go:47): Lean: Deleting the generated-name branch leaves generatedJobNames with no production callers (only notify_comment_failed_jobs_test.go:144); remove the 23-line map and that assertion, or this dead state will keep looking like compiler behavior. - Document generated permissions and preserve author comments #75615 (comment)
  3. Review (pkg/workflow/compiler_permission_comments.go:227): The generated top-level permissions block never receives the source comment mapping, so author comments on frontmatter-level permissions are silently dropped. This contradicts the preservation goal and the added TestDocumentPermissionComments expectation for # Agent permissions / # Agent context. Pass sources[string(constants.AgentJobName)] (or equivalent) here so root permission comments are copied as well. - Document generated permissions and preserve author comments #75615 (comment)
  4. Review (pkg/workflow/compiler_permission_comments.go:218): [/diagnosing-bugs] This new parse turns previously-compiling output into a hard compile error. documentPermissionComments now runs yaml.Unmarshal over the entire generated workflow and returns an error on failure. Any existing rendering quirk now breaks gh aw compile. Examples: the unquoted GH_AW_CURRENT_WORKFLOW_REF line when the test workflow name contains : , and the bare push line produced by on: "push". Disabling this call makes TestPullRequestDraftFilter, TestASCIILogoAlignment, TestOutputCommentJobGeneration, and the WASM golden tests pass again. - Document generated permissions and preserve author comments #75615 (comment)
  5. Review (pkg/workflow/compiler_yaml.go:311): [/codebase-design] This call site applies the new post-processing to every compiled workflow, so any failure in it aborts the whole compile. Keep the annotation pass non-fatal here, or make it a separate step that runs after validation succeeds. - Document generated permissions and preserve author comments #75615 (comment)
  6. Fix failing check build-wasm (FAILURE): https://github.com/github/gh-aw/actions/runs/42379859988/job/128425101317.
  7. Fix failing check build-wasm (FAILURE): https://github.com/github/gh-aw/actions/runs/42345389466/job/128321998268.
  8. Fix failing check impacted-go-tests (FAILURE): https://github.com/github/gh-aw/actions/runs/42379859988/job/128425101359.
  9. Fix failing check impacted-go-tests (FAILURE): https://github.com/github/gh-aw/actions/runs/42345389466/job/128321998127.
  10. Fix failing check safe_outputs (FAILURE): https://github.com/github/gh-aw/actions/runs/42379859985/job/128426730446.

Once you start work, post this work summary as a PR comment without the leading Copilot mention, including the Sous-chef head, work, and state lines below, to record that the assignment is running. Apply the necessary fixes on this PR's existing branch, reply to each listed review thread and resolve it when addressed. Ignore feedback already answered or resolved; stop when only human review or CI remains. Do not merge or trigger CI.

Sous-chef requested-head: 81a01f4
Sous-chef requested-work: 06277ed364e4da9af5376c788d4f97e51ff9a12687cd6351ed0b4830b811afaf 1ed51f099d6ffdfb059d8466530ada585a9e0b16458fc17062f693dfd80aad53 32abcacef7f824e01419bd14c3c88a8d1bc90ea836d0f93b2e548217e6481a80 42e5d572d9d75b7168fe7d0aeda0717cc07e65ed240f6d299e6fec661214f1ac 5d1f8f41096d869643fed9e9195a4446f016727b92a6ca7ec872fcd9eabff2cd 8acb61a077717e3a460018aacdfde96fd489f77606cd36169e2328d9079b75bb c7cf93e497befdd5e698d00101b0703e4101fe4133d86d433f7c170d07402b7e
Sous-chef requested-state: 91511291ad408787af41ea49536a0f76d5e900370fe1024d247edc358620cd4a

Generated by 👨🍳 PR Sous Chef · pi · haiku45 · ~6 AIC · ⌖ ~8 AIC · ⊞ 1.2K · ◷
Comment /souschef to run again

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>

Copilot AI commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

@copilot

Copilot assignment requested for the following outstanding work:...

Sous-chef requested-head: 81a01f4
Sous-chef requested-work: 06277ed364e4da9af5376c788d4f97e51ff9a12687cd6351ed0b4830b811afaf 1ed51f099d6ffdfb059d8466530ada585a9e0b16458fc17062f693dfd80aad53 32abcacef7f824e01419bd14c3c88a8d1bc90ea836d0f93b2e548217e6481a80 42e5d572d9d75b7168fe7d0aeda0717cc07e65ed240f6d299e6fec661214f1ac 5d1f8f41096d869643fed9e9195a4446f016727b92a6ca7ec872fcd9eabff2cd 8acb61a077717e3a460018aacdfde96fd489f77606cd36169e2328d9079b75bb c7cf93e497befdd5e698d00101b0703e4101fe4133d86d433f7c170d07402b7e
Sous-chef requested-state: 91511291ad408787af41ea49536a0f76d5e900370fe1024d247edc358620cd4a

Work is underway: merge latest main; address the permission-comment preservation and dead-state review notes; inspect the reported CI failures; then validate, scan, and push the focused fixes. No workflow will be dispatched.

…ted-permissions

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
@pelikhan

pelikhan commented Nov 7, 2026

Copy link
Copy Markdown
Collaborator

@copilot resolve the merge conflicts on this branch.

Copilot AI and others added 2 commits November 7, 2026 15:30
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…ted-permissions

# Conflicts:
#	.github/workflows/pr-specification-reviewer.lock.yml

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

@copilot resolve the merge conflicts on this branch.

Resolved and pushed in c479c91. Merged the latest main and regenerated the conflicted workflow lock file, preserving permission-comment changes. All 360 workflows compiled; focused, WASM golden, and sampled impacted tests passed. Existing custom-lint findings and lint/CodeQL timeouts prevent a fully clean validation gate.

@pelikhan
pelikhan merged commit 8322593 into main Nov 7, 2026
45 of 46 checks passed
@pelikhan
pelikhan deleted the copilot/fix-undocumented-permissions branch November 7, 2026 15:53
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This pull request is included in a new release.

Release: v1.2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v1.0.1 lock files still omit permission comments (zizmor pedantic undocumented-permissions)

4 participants