Assuming you're :+1: to land this @scshitole, could you try cutting a 0.13 tag and pushing it after? Once we confirm this creates a working release of the provider I can update the documentation for first-time users.
@scshitole Thanks for the merge! Did my notes about configuring travis/github make sense? I would love to see if this changeset actually works so I can update the getting started documentation.
This builds on pr #86, making it possible to automatically attach binaries to releases when a tag is pushed to github.
In order for this change to work, you'll need to grant travis the ability to create releases on your behalf by adding the environment variable
GITHUB_TOKEN
here: https://travis-ci.org/f5devcentral/goreleaser-test/settingsThe value needs to be a personal access token with
repo
scope permissions, as generated here: https://github.com/settings/tokens/newAssuming you're :+1: to land this @scshitole, could you try cutting a
0.13
tag and pushing it after? Once we confirm this creates a working release of the provider I can update the documentation for first-time users.Cheers!