auto publish gh release on version tag

[stefan-guggisberg]

Please ensure your pull request adheres to the following guidelines:

• make sure to link the related issues in this description
• when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues

#306

Thanks for contributing!

[codecov]

Codecov Report

Merging #331 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #331   +/-   ##
=======================================
  Coverage   77.12%   77.12%           
=======================================
  Files          28       28           
  Lines        1460     1460           
  Branches      220      220           
=======================================
  Hits         1126     1126           
  Misses        334      334

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f200ac1...b2db0da. Read the comment docs.

[stefan-guggisberg]

@tripodsan @trieloff the 'auto gh release' is triggered by a new version tag (v1.2.3). any idea how i can test this without messing with tags and releases?

[tripodsan]

ok, but I think the checkout is not needed.

[tripodsan]

the 'auto gh release' is triggered by a new version tag (v1.2.3). any idea how i can test this without messing with tags and releases?

maybe create tags manually by using a special tag, like: v99.3.1

[trieloff]

Or just mess with it, and then clean up later ;)