Repository navigation
Rewrite the README around the fork and mention it in doc.go - #29
Merged
Merged
Conversation
…ck start, feature snippets, fixes table and compatibility.
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
1 participant
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.
Restructures the README so the first screen says what the fork is and why it exists, then quick start, migration (with the four behaviour changes in an alert box), one snippet per feature, a table of what v1.4.1 fixes with upstream links, compatibility, project status and credits. The original walkthrough is kept in a collapsed block.
Every Go block in the README was extracted and compiled against this branch (
go vetandgo buildclean). The GitHub Markdown API renders the alerts, the three tables and the details block; all badge URLs return 200. The Go Report Card badge was left out because the service now reports itself as retired.The package doc comment gains a sentence naming the fork and pointing to the README and changelog, which closes the Phase 6 pkg.go.dev task.