This doesn't work because changes are evaluated by looking for any file matches, and means if you have a commit with multiple files, some of which match and some of which are actual code files, this rule will prevent CI. Not what you want.
There are [complicated work-arounds](https://stackoverflow.com/questions/73298609/suppress-gitlab-ci-stage-if-push-only-changes-readme-md). A better solution may be to simply manually include `[ci skip]` in the commit message of changes you want to skip CI on.
There are [complicated work-arounds](https://stackoverflow.com/questions/73298609/suppress-gitlab-ci-stage-if-push-only-changes-readme-md). A better solution may be to simply manually include `[ci skip]` in the commit message of changes you want to skip CI on. Alternatively, you can use `git push -o ci.skip`, which works even if there is no commit message (such as when pushing a tag).
