Uniform command descriptions' format #57
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hcsa73
previously approved these changes
Feb 5, 2024
|
Also I think it's a bit weird that some commands' descriptions are in different tenses. I understand the logic, just think it would look best if they were all declarative. For me it can stay like this, it's better to have some rule and this is fine |
hcsa73
previously approved these changes
Feb 5, 2024
Co-authored-by: Henrique Santos <[email protected]>
Co-authored-by: Henrique Santos <[email protected]>
Co-authored-by: Henrique Santos <[email protected]>
hcsa73
approved these changes
Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale followed:
Longdescriptions always end in a full stop (.,!, ...)Provides functionality for ...,Creates a ...,Deletes a ...)