Closed DirtyF closed 6 years ago
On thinking about this, I believe there's nothing much JekyllBot could do here. CI builds are immediately triggered by git push
. So the [ci skip]
attribute would only make sense if its present before the
git push
event.
A similar approach is already followed in practice when JekyllBot updates the History file, irrespective of the changes:
I always forgot to add
[ci-skip]
to documentation commits to avoid triggering a useless CI build. 😕Could @jekyllbot help?