fix(ci): key estate-standard action refs already used by the workflows - #64
Conversation
+ trufflesecurity/trufflehog@f714bf4 Every SHA-pinned `uses:` ref in .github/workflows/ is now present in .github/workflows/actions.lock. The added entries use the exact SHAs already keyed in the estate SSOT (hyperpolymath/standards) lock; no workflow files changed. Entry format matches gh actions-lock v0.0.2 output (ref/commit/owner_id/repo_id); owner/repo ids resolved from the GitHub API. Verified: validate-actions-lock.sh -> exit 0 (was: N missing ref(s)).
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



fix(ci): key estate-standard action refs already used by the workflows
Every SHA-pinned
uses:ref in .github/workflows/ is now present in.github/workflows/actions.lock. The added entries use the exact SHAs already
keyed in the estate SSOT (hyperpolymath/standards) lock; no workflow files
changed. Entry format matches gh actions-lock v0.0.2 output
(ref/commit/owner_id/repo_id); owner/repo ids resolved from the GitHub API.
Verified: validate-actions-lock.sh -> exit 0 (was: 1 missing ref(s)).