Check pr for removed/changed paths
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- ci-cd, documentation
Research direction
Start by reviewing the documentation site's CI and existing broken-link checking setup. Determine how removed or renamed paths can be detected and how redirect coverage should be reported or enforced; done means links into changed documentation paths are checked for redirects without breaking valid builds.
Written by the indexing model from the issue text.
Description
Feature Summary
There is broken link checking but that won't catch existing links elsewhere back into the documentation site. We should be able to at least post a message to check for redirects, if not just check in ci, if a path is (re)moved.
Feature Category
Other
Problem This Solves
Don't break existing links to docs
Proposed Solution
In ci, check for redirect coverage if paths are (re)moved
User Stories
No response
Alternatives Considered
No response
Priority/Impact
None
Examples or References
No response
Additional Context
No response
Are you planning to fix this issue?
No, just reporting the issue
First-time contributor support
- I'm new to contributing and would appreciate guidance on the process
- I'd like help understanding the project structure
- I need assistance with setting up the development environment
- I'm comfortable contributing but new to this project specifically
- Dominant language
- MDX
- Stars
- 9
- Forks
- 9
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from HarperFast/documentation
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
HarperFast/documentation#690 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
HarperFast/documentation#677 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 Half a day Newbie friendliness 88/100
HarperFast/documentation#675 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
HarperFast/documentation#665 ·
Maintainers usually reply within 2 days
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
HarperFast/documentation#478 ·
Maintainers usually reply within 2 days
All issues in HarperFast/documentation
Similar issues
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lirantal/discoprint#32 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
lawndoc/stack-back#122 ·
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
software-development-practices software-development-practices:nist-ssdf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-cao#15860 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day