Add goreleaser & a gh workflow

[Clivern]

Why
It should be handy to get revive binary without installing go. also I want to add revive inside dockerfile without a dedicated stage to build the binary. So I will have a place to get binaries from (related to #489):

curl -sL https://github.com/mgechev/revive/releases/download/vx.x.x/revive_x.x.x_OS.tar.gz | tar xz

How
With this PR, every time you create a tag, release github workflow runs to build binaries (linux, windows, mac) and upload them to releases section on github https://github.com/mgechev/revive/releases. It also add the changelog from commits.

[mgechev]

@Clivern looks like the recent actions have been failing. Interesting why without changes the secret seems to no longer work? https://github.com/mgechev/revive/runs/5102785873?check_suite_focus=true

[Clivern]

@mgechev I think this is related to this PR #590. It doesn't authenticate with gitHub docker registry to push the docker image. I think it can be fixed by adding this step in https://github.com/mgechev/revive/blob/master/.github/workflows/release.yml

      - name: Log into registry
        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login docker.pkg.github.com -u ${{ github.actor }} --password-stdin

Opened a PR for that #630

cc @doniacld

[mgechev]

Thanks for looking into this!

[mgechev]

Getting a similar failure here. For some reason docker doesn't consume the token via stdin properly?

[Clivern]

nope, goreleaser push to ghcr.io while i used docker.pkg.github.com. better to use ghcr, final fix #631

[mgechev]

The release is green now. Thank you for the fixes :)