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.
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.
*Note*: pushing just a tag is a similar scenario, and it is similarly difficult to avoid CI as it's not easy to indicate skip only if the push contains just a tag and nothing else.
*Note*: pushing just a tag is a similar scenario, and it is similarly difficult to avoid CI as it's not easy to indicate skip only if the push contains just a tag and nothing else. This assumes user is using `push --follow-tags` or `push --atomic`.
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).
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).
