manifoldco / manifoldco/torus-cli
Style guide
@ntassone is already working on this.
Since Dec 8, 2016.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
To reduce fragmentation in our CLI and to improve some of the interactions we use, we are going to produce a style guide.
This issue will act as a central hub for all things style guide, which will start with discussion around each major area of input/output.
- [Tables and lists](https://github.com/manifoldco/torus-cli/issues/125)
- [Success, failure, and error states](https://github.com/manifoldco/torus-cli/issues/126)
- [Whitespace and layout](https://github.com/manifoldco/torus-cli/issues/127)
- [Input prompts](https://github.com/manifoldco/torus-cli/issues/128)
- [Rich formatting](https://github.com/manifoldco/torus-cli/issues/129)
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.
Assessment
This issue has not been assessed yet.