Repository navigation
chore: enforce security hardening for GitHub Actions workflows - #10038
Merged
paulbalandan merged 5 commits intoMar 15, 2026
Merged
Conversation
Member
Author
Yes. It actually can update the pinned SHA. It has done this to my other repo.
It uses the reusable workflow from |
paulbalandan
force-pushed
the
security-hardening
branch
from
March 14, 2026 17:51
cd0db76 to
f5bf01c
Compare
paulbalandan
force-pushed
the
security-hardening
branch
from
March 14, 2026 17:56
f5bf01c to
fd357a8
Compare
Member
I'm getting blind - I haven't noticed that it links to the repo... |
michalsn
approved these changes
Mar 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Ref: https://docs.github.com/en/actions/reference/security/secure-use
Checklist: