Outline language for flintlock CLI #604
Labels
help wanted
Requires help from contributors to get done
kind/feature
New feature or request
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Second part of #601, building on the workflows from #602.
In either a googledoc or in comments on this thread, outline the language for a flintlock cli.
These will be a group of verbs and nouns which when combined will allow operators to intuitively fulfil the workflows established in #602.
This ticket is considered closed when the language has been reviewed and accepted by the team.
The text was updated successfully, but these errors were encountered: