neo/middleman-gh-pages — pull request #16 by rmm5t (2013-12-19 21:24:09+00:00)
Title: Customizing Commit Messages

I've been experimenting with different continuous integration/deployment services lately. Not all are smart enough to skip builds on the gh-pages branch (specifically, I'm talking about Codeship), but one way around this is to add a message like "[skip ci]" to the commit message to avoid the build.

So, what I'd like to suggest is an ability to customize the commit message that gets pushed to the gh-pages branch. I'm happy to code this up, but I wanted to get some buy-in for this feature first. I'm also looking for some guidance of how you'd like this implemented, because there are several ways to potentially handle this.

1. Allow a message argument to add a suffix to the publish task's commit message (meh)
1. Allow for an env variable to specify a suffix for the commit message (easy)
1. Build in some form of configurable commit message template (probably unnecessarily complex)
1. Always add "[skip ci]" to commit messages (easy, but not exactly ideal and limiting)

Thoughts?