[ci skip] flag shows up in commit message when it wasn't called

I replicated the experiment in the Wiki (GitHub version). When I made my first commit, the commit messages are showing up as dvc repro [ci skip]. I wouldn’t expect to see [ci skip] if I didn’t include a flag for that, and in fact, I’m sure the CI ran! It might help me avoid confusion if we avoid printing that flag in commit messages except when it is explicitly called by the user.

[shcheklein]

The way I understand the problem (please @andronovhopf correct me if I’m wrong) is that the message does not look nice on those automated commits, it’s confusing since not that many people are aware about this convention (I believe it’s close to 0), it looks like some noise in the history (similar to the __test__ issue), etc.

The point is that if we can in our action somehow distinguish those w/o relaying on the message we can avoid this special mark and just use regular message.

[DavidGOrtega]

Closed since right now the workflow does not push back to remote anymore.