microsoft / microsoft/react-native-windows
Links to Pluralsights always return 403s when checked by unbroken
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
Our CI checks links in our docs using unbroken. For some reason, working Pluralsight links keep reporting failure.
Steps To Reproduce
Failed build log line: https://dev.azure.com/ms/react-native-windows/_build/results?buildId=232329&view=logs&j=c91ffb0c-93c6-5124-b5e5-2d77344377c2&t=1b2d5bd1-20f5-5a7b-1ec2-ef2ad101a8b1&l=14
Expected Results
No response
CLI version
npx react-native --version
Environment
npx react-native info
Target Platform Version
No response
Target Device(s)
No response
Visual Studio Version
No response
Build Configuration
No response
Snack, code example, screenshot, or link to a repository
No response
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 with the linked Azure build log and inspect how the documentation CI uses unbroken to check Pluralsight links. Reproduce the reported 403 for a working Pluralsight URL, then identify the relevant checker configuration or entry point. Done means the link is checked successfully or the false failure is clearly handled and verified in CI.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100