pingcap / pingcap/docs-tidb-operator
Broken Link Detected
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 129
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
Summary
| Status | Count |
|---|---|
| π Total | 797 |
| β Successful | 769 |
| β³ Timeouts | 0 |
| π Redirected | 0 |
| π» Excluded | 26 |
| β Unknown | 0 |
| π« Errors | 2 |
Errors per input
Errors in en/monitor-a-tidb-cluster.md
- [404] https://raw.githubusercontent.com/pingcap/tidb-operator/refs/heads/%7B%7B%7B%20.tidb_operator_release_branch%20%7D%7D%7D/hack/get-grafana-dashboards.sh | Failed: Network error: Not Found
Errors in zh/monitor-a-tidb-cluster.md
- [404] https://raw.githubusercontent.com/pingcap/tidb-operator/refs/heads/%7B%7B%7B%20.tidb_operator_release_branch%20%7D%7D%7D/hack/get-grafana-dashboards.sh | Failed: Network error: Not Found
Contributor guide
No contributing guide indexed for this repository
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 with en/monitor-a-tidb-cluster.md and zh/monitor-a-tidb-cluster.md, then inspect the linked GitHub Actions output to understand why the templated branch URL returns 404. Verify the corrected links with the repository's link checker; done means both documents no longer report this broken link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100