Skip to content

Command naming conventions #15062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2021
Merged

Command naming conventions #15062

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions contributing/code/conventions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,3 +234,11 @@ of the impacted component:
This task is mandatory and must be done in the same pull request.

.. _`@-silencing operator`: https://www.php.net/manual/en/language.operators.errorcontrol.php

Naming Commands and Options
---------------------------

Commands and their options should be named and described using the English
imperative mood (i.e. 'run' instead of 'runs', 'list' instead of 'lists'). Using
the imperative mood is concise and consistent with similar command-line
interfaces (such as Unix man pages).