This makes it so that the main CI workflow will only trigger if a change is made to a code file in desktop_version/ (as the CI is only for desktop_version/), or if the CI file itself is changed.
The CI workflow for Android will only trigger if Android-specific code could have changed. This includes all code that is definitely Android-specific (e.g. Java files), but also C/C++ files that have __ANDROID__ ifdefs.
By submitting this pull request, I confirm that...
[x] My changes may be used in a future commercial release of VVVVVV
[x] I will be credited in a CONTRIBUTORS file and the "GitHub Friends"
section of the credits for all of said releases, but will NOT be compensated
for these changes
This makes it so that the main CI workflow will only trigger if a change is made to a code file in
desktop_version/(as the CI is only fordesktop_version/), or if the CI file itself is changed.The CI workflow for Android will only trigger if Android-specific code could have changed. This includes all code that is definitely Android-specific (e.g. Java files), but also C/C++ files that have
__ANDROID__ifdefs.Unfortunately, it's not possible to reuse the same list of paths across two different event trigger types. So we have to copy-paste here.
Legal Stuff:
By submitting this pull request, I confirm that...
CONTRIBUTORSfile and the "GitHub Friends" section of the credits for all of said releases, but will NOT be compensated for these changes