文档链接 404
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 31
Description
Error 报告
Please answer the following questions before submitting your issue. Thanks!
-
What is the document directory for the problem?
See this PR https://github.com/pingcap/docs-cn/pull/17030, which fixed 404 links for one branch. This PR has been cherry-picked to
release-8.0andrelease-7.5branches, but 404 links also exist in other branches. Because cherry-picking to earlier branches might cause conflicts and different branches might have different 404 links, the original fix PR wasn't cherry-picked to all the other active branches.Notes:
- Different branches might have different 404 links.
- Before you create a PR to a corresponding
release-xbranch, make sure the branch is active. You can check the active versions by clicking the version box on the top left corner of https://docs.pingcap.com/tidb/stable. Only update active branches because updating to inactive branches won't show on the docs.pingcap.com site.
-
How would you like to improve it?
It would be better to fix all 404 links for all branches, but this can take a lot of time to check and fix them all. If you get some time and have interest, welcome to help create a PR or PRs to help fix them.
Handling progress:
- Fix 404 broken links in release-7.6
- Fix 404 broken links in release-7.4
- Fix 404 broken links in release-7.1
- Fix 404 broken links in release-6.5
- Fix 404 broken links in release-6.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR 17030 and the linked release branches, then use the version selector on docs.pingcap.com/tidb/stable to identify active branches. Check each active branch for broken links and address the 404 links in branch-specific PRs; completion means the listed active branches no longer contain the identified broken links.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100