Skip to content

Conversation

@2bndy5
Copy link
Contributor

@2bndy5 2bndy5 commented Sep 4, 2025

@2bndy5 2bndy5 mentioned this pull request Sep 4, 2025
@2bndy5 2bndy5 force-pushed the review-ci branch 3 times, most recently from 46043f7 to aaba6a3 Compare September 4, 2025 07:19
@codecov
Copy link

codecov bot commented Sep 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.25%. Comparing base (105ced2) to head (37219ca).
⚠️ Report is 17 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   98.25%   98.25%           
=======================================
  Files          23       23           
  Lines        1886     1886           
=======================================
  Hits         1853     1853           
  Misses         33       33           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@2bndy5 2bndy5 marked this pull request as ready for review September 4, 2025 07:43
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This enables zizmor per cpp-linter/.github#46

I suppose we could lock the zizmor version with uv.
But most analysis by zizmore is skipped when GH_TOKEN (or --token) is not provided.

uvx zizmor .github/workflows/*.yml
 INFO zizmor::registry: skipping impostor-commit: can't run without a GitHub API token                                      
 INFO zizmor::registry: skipping ref-confusion: can't run without a GitHub API token
 INFO zizmor::registry: skipping known-vulnerable-actions: can't run without a GitHub API token
 INFO zizmor::registry: skipping forbidden-uses: audit not configured
 INFO zizmor::registry: skipping stale-action-refs: can't run without a GitHub API token
 INFO audit: zizmor: 🌈 completed .github\workflows\analyze-workflows.yml                                                   
 INFO audit: zizmor: 🌈 completed .github\workflows\codeql.yml                                                              
 INFO audit: zizmor: 🌈 completed .github\workflows\docs.yml                                                                
 INFO audit: zizmor: 🌈 completed .github\workflows\labeler.yml                                                             
 INFO audit: zizmor: 🌈 completed .github\workflows\pre-commit.yml
 INFO audit: zizmor: 🌈 completed .github\workflows\release-drafter.yml
 INFO audit: zizmor: 🌈 completed .github\workflows\release.yml
 INFO audit: zizmor: 🌈 completed .github\workflows\stale.yml
 INFO audit: zizmor: 🌈 completed .github\workflows\tests.yml
No findings to report. Good job! (19 suppressed)

- adjust CI matrix about tested clang versions and switch back to ubuntu-latest
- pin actions to their SHA instead of using their tags
- change dependabot updates to monthly check
- rewrite release CI (per cpp-linter/.github#41)
- explicitly specify permissions needed
- add zizmor static analysis
@2bndy5 2bndy5 merged commit d68d320 into main Sep 4, 2025
40 checks passed
@2bndy5 2bndy5 deleted the review-ci branch September 4, 2025 10:56
2bndy5 added a commit that referenced this pull request Sep 4, 2025
Some permissions were in adequate after merging #151.
This was hard to predict because the permission requirements
changed between PR and push events to main.
@2bndy5 2bndy5 mentioned this pull request Sep 4, 2025
2bndy5 added a commit that referenced this pull request Sep 4, 2025
Some permissions were in adequate after merging #151.
This was hard to predict because the permission requirements
changed between PR and push events to main.
@2bndy5 2bndy5 mentioned this pull request Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants