Repository navigation
Conversation
The 'submit a PR' link in README_zh pointed at a v5.0-era page (blob/v5.0/CN/modules/ROOT/pages/v5.0/32.adoc) that no longer exists (404). Point it at the current CN contribution guide instead, which documents the full PR submission flow (issue association, CLA, review). Signed-off-by: zhang1939 <13942782872@163.com>
|
🚀 IvorySQL-Docs Preview Ready
|
This branch was previously deployed
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.
Summary
The
提交PRlink in README_zh.md points at a v5.0-era page (blob/v5.0/CN/modules/ROOT/pages/v5.0/32.adoc) that returns 404 — the page numbering was restructured long ago. Point it at the current CN contribution guide (CN/modules/ROOT/pages/8.1.adoc), which documents the full submission flow: issue association (Fixes #123), CLA signing, and the review process.Validation
Companion of the fork-sync fix already merged in #338; the master counterpart of this link fix is submitted separately.