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
All repos should not test everything against unrelated tests #121
Comments
Something like this should do it:
|
If you would like to work on this, just drop in a comment. cc @cpanato , as this might need some wider coordination. |
Hello, |
Hi, I can work on this. |
@n3k0m4 Hi, if you want to make other repo combinations, it's fine by me. |
awesome, thanks @deobieta / @n3k0m4 I recommend you both collaborate to work out an approach, you could always work together in a Google doc or whatever medium you like and me and @cpanato can comment and help out. Once you have an approach nailed down, we can then move to implementation. Last of all if you're both interested, this might make a nice article for blog.sigstore.dev. |
I have made the Google Docs file for the changes. Please, request the edit rights and notify me here to grant them. If you have any concerns about my changes, you can put comments directly in the doc. |
@lukehinds @cpanato Should actions run on forked repos? |
it can, but only the jobs that does not need access to GCP |
@cpanato I opened a PR to Cosign, could you please check it out. If there is anything you would like me to change, I would be happy to fix it. |
reopening, not all work is done :) |
@lukehinds @cpanato @n3k0m4 I left some notes in the Google Docs file about some approaches we can choose from to improve Github workflows use. Any help, comment or suggestion is welcomed. Thank you. |
A lot of repos are running unit / integration tests against changes such as a markdown edit.
This causes unnecessary use of resources and not in the interest of sustainable computing.
We should find some way to skip CI runs, perhaps based on extensions, .txt, .md
The text was updated successfully, but these errors were encountered: