Skip to content
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.

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

Absurdly strict grammatical point #882

Closed
cjfryer opened this issue Mar 5, 2024 · 0 comments · Fixed by #892
Closed

Absurdly strict grammatical point #882

cjfryer opened this issue Mar 5, 2024 · 0 comments · Fixed by #892

Comments

@cjfryer
Copy link
Member

cjfryer commented Mar 5, 2024

We say:

The Git convention is to write these in the present tense

and no full stop. The Git convention is to write these in the present tense.

But tense is irrelevant: commit messages should be written in the imperative mood. That is: they should be commands which bring the repository to a desired state.

The example we give is:

Leverage best-of-breed synergies going forward

which is obviously in the present tense. But it could be re-written as:

Leverages best-of-breed synergies going forward

and still be in the present tense.

What is to be done?

Just as we append "by zombies" to a clause to reveal the passive voice, we can vouch safe the imperative mood by prepending a silent "please" thus:

[please] Leverage best-of-breed synergies going forward

@cjfryer cjfryer linked a pull request Apr 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant