opencontainers / opencontainers/distribution-spec
Notational conventions
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 260
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 1
Description
https://github.com/opencontainers/distribution-spec/blob/main/spec.md#pull reads
In a successful response, the
Content-Typeheader will indicate the type of the returned manifest.
In order to follow the notation convention, this should read
In a successful response, the Content-Type header MUST indicate the type of the returned manifest.
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
Open spec.md at the Pull section linked in the issue and compare its wording with the specification's existing notation conventions. Change the response requirement to use MUST, then review the surrounding text to confirm the convention is applied consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100