-
Notifications
You must be signed in to change notification settings - Fork 107
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
Update to use docopt.go
import which should be ok since Go 1.13
#75
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Waldemar Quevedo <[email protected]>
docopt.go
import which should be ok nowdocopt.go
import which should be ok since Go 1.13
@mboersma ping |
Closing since seems that project is not maintained anymore, but this should be fine in case someone wants to pick this up. |
@wallyqs my apologies for not following up! You're right that the project is unmaintained now, and I'm reluctant to make any changes that would imply it's still supported. I still think docopt is a groovy idea, but the project founder has moved on and none of us have been able to contact him for years. 😞 |
@mboersma no worries! I liked docopt since it was great for prototyping when using it in Ruby, thanks for the reply :) |
Would be great to add 1.16 and 1.17 to CI with this PR as well @wallyqs |
@shakefu thanks, just added 👍 |
Updated the repository to use
github.com/docopt/docopt.go
which since version Go 1.13 should work ok with Go modules (I know because other project I help maintainnats.go
was one of the first projects ending with.go
being able to use this approach without issues 😅 )Signed-off-by: Waldemar Quevedo [email protected]