Skip to content

Run zizmor on pull requests - #849

Merged
samueltardieu merged 2 commits into
mainfrom
push-nurusykvwyko
Sep 30, 2026
Merged

Run zizmor on pull requests#849
samueltardieu merged 2 commits into
mainfrom
push-nurusykvwyko

Conversation

@samueltardieu

@samueltardieu samueltardieu commented Sep 30, 2026

Copy link
Copy Markdown
Member

No description provided.

@samueltardieu
chore(ci): fix the security findings reported by zizmor
18084bc 
- Pin every third-party action to a commit hash (with the version tag
  as a comment) instead of a mutable tag.
- Set `persist-credentials: false` on every checkout, as none of the
  jobs push back to the repository.
- Restrict permissions to `contents: read` at the job level, with an
  empty top-level block, instead of relying on the defaults.
- Pass `github.base_ref`, the base branch step output and
  `matrix.toolchain` through environment variables rather than expanding
  them directly into shell scripts.
@samueltardieu
chore(ci): run zizmor on pull requests
bf3f058 
Audit the GitHub Actions workflows with zizmor so that new security
findings are reported on pull requests through code scanning.
@github-advanced-security

github-advanced-security AI commented Sep 30, 2026

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions

github-actions Bot commented Sep 30, 2026

Copy link
Copy Markdown

📊 iai-callgrind Benchmark Results

➡️ 20 Unchanged (within ±0.1%)

Click to expand
Benchmark Instructions
iai_algos::corner_to_corner_astar 167,075
iai_algos::corner_to_corner_bfs 3,097,176
iai_algos::corner_to_corner_bfs_bidirectional 3,066,594
iai_algos::corner_to_corner_dfs 2,956,482
iai_algos::corner_to_corner_dijkstra 3,755,146
iai_algos::corner_to_corner_fringe 124,497
iai_algos::corner_to_corner_idastar 157,513
iai_algos::corner_to_corner_iddfs 3,796,528
iai_algos::no_path_astar 4,015,347
iai_algos::no_path_bfs 3,004,301
iai_algos::no_path_bfs_bidirectional 2,964,634
iai_algos::no_path_dfs 2,848,686
iai_algos::no_path_dijkstra 3,729,474
iai_algos::no_path_fringe 3,008,422
iai_edmondskarp::wikipedia_example_dense 22,370
iai_edmondskarp::wikipedia_example_sparse 46,095
iai_kuhn_munkres::kuhn_munkres_size_128 4,211,200
iai_kuhn_munkres::kuhn_munkres_size_32 239,050
iai_kuhn_munkres::kuhn_munkres_size_64 1,199,842
iai_separate_components::bench_separate_components 16,458,596

✅ All benchmarks unchanged

iai-callgrind measures instructions executed, which is deterministic and not affected by system load.

@samueltardieu
samueltardieu added this pull request to the merge queue Sep 30, 2026
Merged via the queue into main with commit dfffc6b Sep 30, 2026
14 checks passed
@samueltardieu
samueltardieu deleted the push-nurusykvwyko branch September 30, 2026 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@samueltardieu @github-advanced-security