This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients FFY00, vstinner
Date 2020-05-07.18:00:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588874448.45.0.474043182646.issue40548@roundup.psfhosted.org>
In-reply-to
Content
> The workaround presented at https://github.community/t5/GitHub-Actions/Feature-request-conditional-required-checks/m-p/51344/highlight/true#M8157 seems pretty reasonable. And it seems like travis is alerady doing the same thing as it doesn't have native support to skip runs based on path changes.

I suppose that Steve Dower mentioned the following part of .azure-pipelines/prebuild-checks.yml:
----------------
- script: |
   if ! git diff --name-only $(diffTarget) | grep -qvE '(\.rst$|^Doc|^Misc)'
   then
     echo "Only docs were updated: tests.run=false"
     echo "##vso[task.setvariable variable=run;isOutput=true]false"
   else
     echo "Code was updated: tests.run=true"
     echo "##vso[task.setvariable variable=run;isOutput=true]true"
   fi
  displayName: Detect source changes
  name: tests
----------------

I understood that he proposed to port it inside the Windows job of GitHub actions (.github/workflows/build.yml).

I propose the following plan:

* Always run GitHub Action jobs
* Make Windows 64-bit job mandatory
* And only then try to skip documentation-only changes
History
Date User Action Args
2020-05-07 18:00:48vstinnersetrecipients: + vstinner, FFY00
2020-05-07 18:00:48vstinnersetmessageid: <1588874448.45.0.474043182646.issue40548@roundup.psfhosted.org>
2020-05-07 18:00:48vstinnerlinkissue40548 messages
2020-05-07 18:00:48vstinnercreate