Golang project/library based on Makefile
makefile-go temaplate has a bold assumption and convention like the followings:
- Your project use dep
- Your project have VERSION file as version origin
- Your project have tests and tests run in travis (and appveyour)
- README.md is generated from godoc (no more doc duplicity/mismatch)
- Your app project is released to github releases
- vendor dir is gitignored (vendor isn't commited - https://github.com/golang/dep/blob/master/docs/FAQ.md#should-i-commit-my-vendor-directory)
- run test with coverege (https://github.com/pierrre/gotestcover#deprecated)
- generate github token
gem install travistravis encrypt 'GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>'
make releaseuse content of VERSION file to create new tag- travis-ci automatically build app and release it
make releaseuse content of VERSION file to create new tag