Repository home page does not show v3
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Landing on the repository one can see all spec versions up to 2.2
There is a branch with a v3 that is not visible unless one knows where to look.
Wondering what's the situation, one can imagine that maybe:
- v3 was never completed and did not get merged
- v3 is not merged into master due to a simple oversight
- the is just a different convention in managing the branches
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
Inspect the repository home page and the v3 branch, comparing the versions currently visible up to 2.2 with the branch contents. Determine whether v3 should be surfaced or whether its branch status needs clarification; done means the repository landing page accurately communicates the available specification versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100