diff options
author | bep <bjorn.erik.pedersen@gmail.com> | 2015-04-06 15:15:51 +0200 |
---|---|---|
committer | bep <bjorn.erik.pedersen@gmail.com> | 2015-04-06 15:15:54 +0200 |
commit | be25acae284e0b1bab0dead34298537f144e774b (patch) | |
tree | 053f202f63079eb2baf143a5c596d0447b03749a /README.md | |
parent | be1b7f67d3f02fe9d100f31b61c5222220e4dccb (diff) |
Fix README part about missing Windows tests
We now have AppVeyor.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -100,8 +100,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) will catch most things that are missing. The exception: Windows. We run on Windows from time to time, but if you have access, please check on a Windows machine too. - + * 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 |