Skip to content
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

Create a short guide on how to pin urfave/cli v1 #928

Closed
coilysiren opened this issue Nov 14, 2019 · 2 comments
Closed

Create a short guide on how to pin urfave/cli v1 #928

coilysiren opened this issue Nov 14, 2019 · 2 comments
Labels
help wanted please help if you can! kind/documentation describes a documentation update status/confirmed confirmed to be valid, but work has yet to start

Comments

@coilysiren
Copy link
Member

coilysiren commented Nov 14, 2019

This is conceptually related to #921


Frequently, people will opt for pinning v1 rather than migrating to v2. This is totally fine and something we generally are comfortable with - so long as we aren't flooded with "how do I pin v1" Github issues. In service of that, we should create a readme describing how to pin the latest v1 version.

Examples of PRs where people ping v1:

@coilysiren coilysiren added the kind/documentation describes a documentation update label Nov 14, 2019
@coilysiren coilysiren changed the title Create a short guide on how to lock urfave/cli v1 Create a short guide on how to pin urfave/cli v1 Nov 14, 2019
@coilysiren coilysiren added the help wanted please help if you can! label Nov 14, 2019
@coilysiren coilysiren added the status/confirmed confirmed to be valid, but work has yet to start label Nov 27, 2019
@coilysiren
Copy link
Member Author

Here's a blog post that's helpful => https://blog.golang.org/migrating-to-go-modules

@coilysiren
Copy link
Member Author

I consider https://blog.golang.org/migrating-to-go-modules the best possible example here, so I'm closing this 👋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted please help if you can! kind/documentation describes a documentation update status/confirmed confirmed to be valid, but work has yet to start
Projects
None yet
Development

No branches or pull requests

1 participant