We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi!
Would it be possible to update this package to be compatible with Go modules?
I think when I try to import it right now it's looking for a v5 module and failing, based on my understanding of https://github.com/golang/go/wiki/Modules#semantic-import-versioning, because of the v5 in the import path:
$ go build go: finding github.com/salsita/go-pivotaltracker/v5/pivotal latest go: finding github.com/salsita/go-pivotaltracker/v5 latest go: downloading github.com/salsita/go-pivotaltracker/v5 v5.0.0-20181227212238-6d1834bca959 build github.maxmind.com/maxmind/mm_website.git/go/check-go-version: cannot find module for path github.com/salsita/go-pivotaltracker/v5/pivotal
I'm not sure the best way to address this unfortunately.
Thank you!
The text was updated successfully, but these errors were encountered:
Oh, using the gopkg.in import path works it seems!
Sorry, something went wrong.
This is an issue when trying to work with a fork of the repo too, which is useful when working on improvements!
I think that we could do https://github.com/salsita/go-pivotaltracker/compare/enable-go-modules?expand=1 and tag the repo as v3.0.0, I don't see any other way forward.
v3.0.0
No branches or pull requests
Hi!
Would it be possible to update this package to be compatible with Go modules?
I think when I try to import it right now it's looking for a v5 module and failing, based on my understanding of https://github.com/golang/go/wiki/Modules#semantic-import-versioning, because of the v5 in the import path:
I'm not sure the best way to address this unfortunately.
Thank you!
The text was updated successfully, but these errors were encountered: