Actionable error experience for PR view when 403s happen
Open
Requests and ideas
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Short summary
_No response_
### Affected version or release
_No response_
### Installation context
_No response_
### What happened?
This doesn't give me a clear next step as a user.
### Steps to reproduce
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reproducing the 403 in the PR view described by the screenshot and inspect the current error experience. Define an actionable next step for users, then verify that the PR view presents it when the 403 occurs.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100