-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix(issue 295): ensure inputs don't leak to child processes #296
Conversation
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.
Is it feasible/valuable to have a test for this?
Not sure. Ultimately it depends on an internal behaviour of GitHub Actions that ends in a child process. so I don't think we can test that? At least I don't think we can do any kind of full integration test here. Maybe we can and should have a basic unit test that stubs |
yes please, let's have a unit test for this behavior |
I'm sure you noticed but CI is red @AlanSl |
closes #295
I split this out from the provenance work because it's a separate issue, posting this as an example implementation if we do think it's something worth doing. Not sure if it should have tests or not or if it's really possible to test?