-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using semantic-release
+ conventional commits to do releases
#23
Comments
@joshmcarthur do you have any thoughts or opinions on this? |
I think this is the key for me. I'm happy to faciliate it getting done (such as providing access to releasers, etc), but if it's something only happening intermittently, it seems a low-value automation. |
I agree it's not high priority given how rarely we do a release, but i do think it has value since currently we need your time if we want do any releasing 😅 For me this is also a good opportunity to learn how gem publishing & management actually works so I'm happy to do the actual work of setting everything up - I just first wanted to check if you were happy with the commit convention first. |
I think it would be good if we automated the release process to reduce the risk and overhead around doing releases - especially since we don't do that man releases which makes it easy to forgot the process.
This pairs well with using conventional commits as that will allow us to generate the changelog & version based on the commits.
The text was updated successfully, but these errors were encountered: