Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #947 +/- ##
=======================================
Coverage 90.05% 90.05%
=======================================
Files 65 65
Lines 12036 12036
=======================================
Hits 10839 10839
Misses 1197 1197 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
One other small comment. We use "octopin" from the eclipse foundation (and with monorepo support of prek it is nicely separate in a separate .pre-commit.yaml - see https://github.com/apache/airflow/blob/main/dev/.pre-commit-config.yaml - to nicely keep hash-commits updaed for our actions with comments about the version used. Also recommended. |
📦 Cargo Bloat ComparisonBinary size change: +0.00% (16.1 MiB → 16.1 MiB) Expand for cargo-bloat outputPR Branch ResultsBase Branch Results |
|
Great work here @j178 👏 You can also enforce SHA pinning as repo policy now (you may already have)
via GitHub Actions policy now supports blocking and SHA pinning actions (August 15, 2025) |
* Hardening github actions * Add config * Fix comment
* Hardening github actions * Add config * Fix comment
| @@ -0,0 +1,14 @@ | |||
| # Configuration for the zizmor static analysis tool, run via pre-commit in CI | |||
There was a problem hiding this comment.
This seems to be misleading. zizmor is run via its own action and currently there is no clear path to run it locally.
There was a problem hiding this comment.
Yeah, this comment should be updated.
There was a problem hiding this comment.
Coming from j178/prek-action#55, was there a reason to prefer a new workflow over the git hook?
There was a problem hiding this comment.
zizmor action supports GitHub advanced security and add inline annotations to changes, so I would prefer using zizmor action.
There was a problem hiding this comment.
Got it. With this setup, what should one do to run it locally?
There was a problem hiding this comment.
I'll just let CI checks it :)
persist-credentials: falseforactions/checkout