-
Notifications
You must be signed in to change notification settings - Fork 113
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
Contact people from https://awesome-go.com/ #20
Comments
I have submitted a pull request for this. |
Probably removing satori's version is too aggressive. May be just add some clarification text additionally to the project description. |
We should do this once we've cut a release and are feeling good about the README file. Right now this project is only going to be usable by people who use Edit: Especially if we're considering more breaking changes. |
The PR has been temporarily closed and will be re-opened after we have a release. |
Removing this from the 2.0.0 milestone, since this is to happen after not before. |
I can reopen this tonight |
@jadr2ddude now that #19 is merged I think you're all good to go. |
The awesome-go PR has been merged. |
I think it would be helpful if we contacted https://awesome-go.com/ and explained the situation
This fork should be added with no doubts, but it's not certain to me whether the original one should be marked explicitly somehow.
The text was updated successfully, but these errors were encountered: