Avoid running tests for changes in .github/* #442

Activity

1. ezio-melotti

   added

   CI

   on Apr 16, 2022
2. TeamSpen210 commented on Apr 16, 2022

   

   TeamSpen210

   on Apr 16, 2022

   More actions

   According to python/cpython#84728 it has to run, so it can complete and allow merging. So instead the folder would need to be added here to skip the actual execution in this case?

   👍React with 👍1Reacted by Ezio Melotti
3. ezio-melotti commented on Apr 16, 2022

   

   ezio-melotti

   on Apr 16, 2022

   MemberAuthor

   More actions

   So instead the folder would need to be added here to skip the actual execution in this case?

   From a quick look it seems that might be enough, but I'm not too familiar with that workflow. @vstinner, what do you think?

   Also note that the original thread linked in one of the messages has received more replies and now links to a couple of GH actions that might be useful.
4. hugovk commented on Apr 16, 2022

   

   hugovk

   on Apr 16, 2022

   Member

   More actions

   Unless maybe for .github/workflows

   Yes, let's keep running for these: we want to know that changes to CI config doesn't break the build :)

   👍React with 👍2Reacted by Alex Waygood and Ezio Melotti
5. vstinner commented on Apr 19, 2022

   

   vstinner

   on Apr 19, 2022

   Member

   More actions

   Unless maybe for .github/workflows, it shouldn't be necessary to run the whole test suite for changes to other files.

   Changing .github/workflows/build.yml or .github/workflows/doc.yml can likely break the CI if a bug is introduced. I wouldn't call this wasting CI resources. Changing .github/ is rare.

   I close the issue.

   👍React with 👍4Reacted by Christian Heimes, Hugo van Kemenade, Jelle Zijlstra and Ezio Melotti
6. vstinner

   closed this as completedon Apr 19, 2022
7. ezio-melotti

   closed this as not plannedon Jul 29, 2022