ChatOps fails when the last commit used [skip ci]

Summary

GitLab ChatOps integration with Slack does not work when the last commit of the default branch skipped the CI with [skip ci].

Running the /somerepo run xxxx results in

Sorry, this chat service is currently not supported by GitLab ChatOps.

This does not reproduce when the commit message is "normal" and the CI is skipped with git push -o ci.skip. Only [skip ci] git message causes this bug.

Steps to reproduce

  1. Set up a ChatOps integration of a project with Slack
  2. Commit something to the project with [skip ci] being in the commit message
  3. Type /project run something into Slack
  4. You will get Sorry, this chat service is currently not supported by GitLab ChatOps. error response
  5. Commit something again, this time without the CI skip flag
  6. Type /project run something into Slack again
  7. This time it works fine

Output of checks

This bug happens also on GitLab.com, as well as with the latest 13.12 on-prem.

Edited by Martin Melka