You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
We say:
gds-way/source/standards/source-code/working-with-git.html.md.erb
Line 110 in d19d71e
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:
which is obviously in the present tense. But it could be re-written as:
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:
The text was updated successfully, but these errors were encountered: