diff options
author | Anthony Fok <foka@debian.org> | 2015-08-04 12:00:08 -0600 |
---|---|---|
committer | Anthony Fok <foka@debian.org> | 2015-08-04 12:00:08 -0600 |
commit | 5505ac0d72d53e49df67fabed2446344d3fe52ee (patch) | |
tree | 7118daa018d9d49b9836112107651cd5e392c1ea /README.md | |
parent | b0416e9befb98c916f2fd80c2bcbb9cde5b72f95 (diff) |
doc: Strip trailing whitespace; other revisions
Make some random and non-comprehensive changes to the
template functions documentation to make them more
consistent.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -101,7 +101,7 @@ We welcome your contributions. To make the process as seamless as possible, we a * Run `go fmt` * Squash your commits into a single commit. `git rebase -i`. It’s okay to force update your pull request. * This [blog article](http://chris.beams.io/posts/git-commit/) is a good resource for learning how to write good commit messages, the most important part being that each commit message should have a title/subject in imperative mode without trailing period: *"Return error on wrong use of the Paginator"*, **NOT** *"Returning some error."* Also, if your commit references one or more GitHub issues, always end your commit message body with *See #1234* or *Fixes #1234*. Replace *1234* with the GitHub issue ID. The last example will close the issue when the commit is merged into *master*. - * Make sure `go test ./...` passes, and `go build` completes. Our [Travis CI loop](https://travis-ci.org/spf13/hugo) (Linux) and [AppVeyor](https://ci.appveyor.com/project/spf13/hugo/branch/master) (Windows) will catch most things that are missing. + * Make sure `go test ./...` passes, and `go build` completes. Our [Travis CI loop](https://travis-ci.org/spf13/hugo) (Linux) and [AppVeyor](https://ci.appveyor.com/project/spf13/hugo/branch/master) (Windows) will catch most things that are missing. ### Building Hugo with Your Changes |