-
Notifications
You must be signed in to change notification settings - Fork 135
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
Support for pull_request #358
Comments
Another use-case: is to test the configuration. For example, I didn't realize that env vars are case-sensitive and ran into this problem
because I had been using |
The OpenZepplin folks mentioned that they would like support for pull requests |
Is there anything stopping delegator from PR events? I believe it should be able to output unsigned attestations if htere's a guard on the sign-attestations step. |
Right. I think signing is the biggest thing though there are some other subtle differences as well. I think we had issues with which git sha we pick up when generating the provenance? I can't exactly remember but I think
|
It would be nice to have |
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
Token is not available within pull_request context. Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Signed-off-by: John Andersen <[email protected]>
* Add plugin helper entrypoint_style_load() to assist with loading auth middleware * Add server CLI arg for Flask middleware loaded via entrypoint style load plugin helper * OIDC auth middleware plugin * Refactor test Service expose url with bound port to Flask app * In preperation for use by flask test app used as OIDC endpoints * Tests for OIDC based auth middleware * Update pip, setuptools, wheel to avoid deprecation warning on dependency install. * Example CI job for GitHub Actions OIDC authenticated notary * Token is not available within pull_request context. * Document OIDC authentication middleware usage with GitHub Actions * Validation of OIDC claims via JSON schema validator Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Related: actions/runner#2417 (comment) Signed-off-by: John Andersen <[email protected]>
…unity#31) * Add plugin helper entrypoint_style_load() to assist with loading auth middleware * Add server CLI arg for Flask middleware loaded via entrypoint style load plugin helper * OIDC auth middleware plugin * Refactor test Service expose url with bound port to Flask app * In preperation for use by flask test app used as OIDC endpoints * Tests for OIDC based auth middleware * Update pip, setuptools, wheel to avoid deprecation warning on dependency install. * Example CI job for GitHub Actions OIDC authenticated notary * Token is not available within pull_request context. * Document OIDC authentication middleware usage with GitHub Actions * Validation of OIDC claims via JSON schema validator Related: slsa-framework/slsa-github-generator#131 Related: slsa-framework/slsa-github-generator#358 Related: actions/runner#2417 (comment) Signed-off-by: John Andersen <[email protected]>
This is a tracking issue for supporting
pull_request
events. Please comment regarding your use case.The text was updated successfully, but these errors were encountered: