Open herbygillot opened 4 years ago
Excuse my ignorance here, I don't know a proper work flow for good release management on github. Please reach out to me with a more detailed suggestion and we'll work something out.
Excuse my ignorance here, I don't know a proper work flow for good release management on github. Please reach out to me with a more detailed suggestion and we'll work something out.
At the very least, pushing a git tag pointing to where in master
represents your release helps as well. With every increment of crush
's version number, make a respective git tag pointing to that point so others can know which points in master
represent the stable releases.
Here's information per what @nu8 was referring to around creating formal releases: https://docs.github.com/en/github/administering-a-repository/managing-releases-in-a-repository
release-it is a tool that automates releasing arbitrary code on github using one extra file in your repo: package.json
ACK, I'll do a 0.2.0 release with a corresponding git tag as soon as the current features stabilise.
Interested in packaging
crush
; thanks.