-
Notifications
You must be signed in to change notification settings - Fork 146
feat: improve refs #1126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: improve refs #1126
Conversation
@ianlewis any ideas why some pre-submit are not running? |
there was a yaml error. |
Yeah, if there is a yaml error they don't show up in the list unfortunately. It's very unintuitive. |
@@ -108,7 +108,7 @@ jobs: | |||
actions: read # Needed to read workflow info. | |||
steps: | |||
- name: Generate builder | |||
uses: slsa-framework/slsa-github-generator/.github/actions/generate-builder@923a5a249d2ea820614a80486c9ef0857ced5321 | |||
uses: slsa-framework/slsa-github-generator/.github/actions/generate-builder@main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it's worth it but I think we could technically unpin generate-builder
if we bring the secure-builder-checkout
out into the reusable worflows.
In that case the rule would be that all actions are unpinned except detect-env
and secure-builder-checkout
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could. But then we pass the same arguments to both secure-builder-checkout
and generate-builder
which seems a little weird. wdut?
Note: some adversarial tests (3 of them) will always show as failing after this PR. |
Co-authored-by: asraa <[email protected]> Signed-off-by: laurentsimon <[email protected]>
Co-authored-by: asraa <[email protected]> Signed-off-by: laurentsimon <[email protected]>
This PR does:
@main