Skip to content

ci: add compliance check workflow for org ruleset #37

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chitcommit merged 1 commit into from
Mar 16, 2026
Merged

ci: add compliance check workflow for org ruleset #37

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
15 changes: 15 additions & 0 deletions .github/workflows/compliance-check.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
name: compliance

on:
push:
branches: [main]
pull_request:

jobs:
compliance:
uses: CHITTYOS/chittyops/.github/workflows/reusable-compliance-check.yml@main
with:
service_name: 'chittycommand'
tier: 3
check_health: true
domain: 'command.chitty.cc'
Comment on lines +10 to +15

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {}

Copilot Autofix

AI 6 months ago

In general, to fix this category of issue you add a permissions: block either at the top (root) of the workflow to apply to all jobs, or under a specific job to apply only there. The block should grant the minimum scopes needed. For workflows that only run checks and do not need to write back to the repository, contents: read is a good baseline. If the reusable workflow needs additional permissions (for example, to update issues or pull requests), those can be added explicitly.

For this specific workflow, the simplest and safest change without altering behavior of the reusable workflow is to declare minimal read-only permissions at the workflow root, just under the name: key and before on:. This ensures the GITHUB_TOKEN available to the compliance job (and thus to the called reusable workflow) is constrained to read repository contents by default. If the reusable workflow requires more permissions, they can still be granted there; our change does not prevent that, but documents and constrains the default from this workflow鈥檚 side. Concretely, in .github/workflows/compliance-check.yml, add:

permissions:
  contents: read

between lines 1 and 3. No imports or additional methods are needed, since this is a YAML configuration change only.

Suggested changeset 1
.github/workflows/compliance-check.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/compliance-check.yml b/.github/workflows/compliance-check.yml
--- a/.github/workflows/compliance-check.yml
+++ b/.github/workflows/compliance-check.yml
@@ -1,4 +1,6 @@
 name: compliance
+permissions:
+  contents: read
 
 on:
   push:
EOF
@@ -1,4 +1,6 @@
name: compliance
permissions:
contents: read

on:
push:
Copilot is powered by AI and may make mistakes. Always verify output.
Loading