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
Worth noting that this project, and related projects, are not specific to GO #15
Comments
Yes! I started it because i felt bad about go release process at that time, I m really happy you saw that far about it. Should it be changed, |
I really like your approach. Renaming would likely be a pain for very little value, so you can just change later if you start to see lots of uses. Again, many thanks for contributing this, it solves a problem that was honestly completely unapproachable for an intermediate developer otherwise. |
I ll keep it open to get back on it later. |
I think it's a bit unfortunate that the names of these packages and repos are all prepended with "go-". It led me to believe that they were specific to go projects, and now I believe they are universally useful CLI tools which provide simple and streamlined utility mechanisms enabling a reasonable and unified "release" process across operating systems and programming languages.
Is my belief correct, or is there something that is Go specific? I will be trying to implement for C++ projects today, so I guess I'll find out. However, if I'm correct, you may want to make that clear on the main readme (because it's really awesome).
The text was updated successfully, but these errors were encountered: