Clarify command annotations for server or client side
Open
Nobody has claimed this yet.
help wanted
kind/enhancement
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Annotations can disable or hide some commands, but it's not clear if they are targeting the client or the server environment.
Here is an incomplete list of these commands:
- experimental (server)
- experimentalCLI (client)
- ostype (server)
- and a new ostype client side could simplify #1362
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 locating the command annotations represented by experimental, experimentalCLI, and ostype in the Docker CLI, then review the related discussion in issue #1362. Document or adjust their server/client targeting, and determine whether a client-side ostype annotation is needed; done means the environments and resulting command behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100