Make CI run on changes to non-code files as well

[madsmtm]

The repository is configured such that specific checks are required to pass before merging; since CI doesn't run on PRs that don't change code, they can't be merged without administrator intervention.

Currently affecting #2126, and has affected many others in the past.

Also, while this definition is currently correct, we might in the future change something so that changes to other files (like markdown files) really should be run through CI.

• Tested on all platforms changed
• Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
• Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
• Created or updated an example program if it would help users understand this functionality
• Updated feature matrix, if new features were added or implemented

[maroider]

Ideally, we'd have CI skip any code-checking steps if no source code was touched, instead of running all the steps all of the time, but that's also a bit more complicated to set up.

[rukai]

LGTM
Running CI on all PRs is not that expensive and is far safer as there are a lot of ways to break things outside of changing code.

[madsmtm]

Ideally, we'd have CI skip any code-checking steps if no source code was touched, instead of running all the steps all of the time, but that's also a bit more complicated to set up.

Also not something neither you nor I can fix, I think it's part of the repo settings that only an admin/"owner" can access?

[maroider]

Also not something neither you nor I can fix, I think it's part of the repo settings that only an admin/"owner" can access?

It's something a more sophisticated CI config could solve.

[madsmtm]

Fair enough, I'll gladly admit I don't know enough about GitHub Actions.

[maroider]

This, while somewhat wasteful, is probably nicer than having to circumvent the "CI passes" check.

We should probably try to get a more granular CI config set up eventually.