docs: fix the link to the migration discussion from v2 to v3#2085
Merged
docs: fix the link to the migration discussion from v2 to v3#2085
Conversation
abitrolly
approved these changes
Apr 1, 2025
Contributor
|
@suzuki-shunsuke nice catch! |
Contributor
Author
Contributor
|
Publish docs job failed https://github.com/urfave/cli/actions/runs/14188563023/job/39748211402 Not sure what is not right for the |
Contributor
|
https://github.com/urfave/gfmrun page doesn't contain any usage lines, the explanation how it works with imports, and why the process fails. |
Contributor
|
Looks like the problem is in processing |
Contributor
Author
|
I opened an issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
This pull request fixes the link to the GitHub Discussion where to discussion how to migrate v2 to v3.
Now the link points to #921 , but this was closed and this is an issue for the migration v1 to v2.
So I created a discussion for the migration v2 to v3.
Which issue(s) this PR fixes:
Special notes for your reviewer:
(fill-in or delete this section)
Testing
(fill-in or delete this section)
Release Notes
(REQUIRED)