RFC-to-be Final Review page: if RFC-to-be is part of a cluster, link to cluster final review page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 8
Description
For a document that is in Final Review and also in a cluster, provide a link to the cluster's Final Review page (https://queue.rfc-editor.org/final-review/CNNN/) on the document's Final Review page (https://queue.rfc-editor.org/final-review/rfcNNNNN/) rather than the general Cluster page (https://queue.rfc-editor.org/clusters/NNN/).
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 tracing the implementation of the document Final Review page at /final-review/rfcNNNNN/ and compare how it identifies and links clusters. Verify the cluster Final Review route at /final-review/CNNN/ and the current general cluster route. Done means a clustered document links to the cluster Final Review page instead of the general Cluster page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100