Skip to content

fix(ci): grant Super-Linter result permissions - #628

Open
atu92345-web wants to merge 2 commits into
NextCommunity:mainfrom
atu92345-web:fix/super-linter-pr-permissions
Open

atu92345-web wants to merge 2 commits into
NextCommunity:mainfrom
atu92345-web:fix/super-linter-pr-permissions

Conversation

@atu92345-web

Copy link
Copy Markdown

Summary\n\n- grant Super-Linter pull-requests: write so it can publish pull-request results\n- grant statuses: write so it can publish commit status checks\n\nFixes #369\n\n## Validation\n\n- git diff --check\n- workflow-only change; full CI will run on this pull request

@deepsource-io

deepsource-io Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

DeepSource Code Review

We reviewed changes in 1839f0e...a278803 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
JavaScript Sep 26, 2026 8:43p.m. Review ↗
Secrets Sep 26, 2026 8:43p.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@atu92345-web

Copy link
Copy Markdown
Author

Hi @jbampton — PR #628 addresses #369 by granting Super-Linter the pull-request/status write permissions needed for its GitHub API result publication. The fork-triggered workflow runs are currently marked �ction_required; could you approve those checks and review the focused change when convenient?

This branch has not been deployed

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

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants