Use imperative present tense verb in example #42

New Issue

GiteaMirror · 2026-02-17T11:37:40-06:00

GiteaMirror commented

2026-02-17 11:37:40 -06:00

Originally created by @apetro on GitHub (Aug 20, 2018).

Originally assigned to: @hutson on GitHub.

While Conventional Commits itself does not specify verb voice and tense for the description, it's common to use imperative, present tense describing what the commit, if applied, does, rather than past tense describing what was done. So adopt this convention in the example, making the commit message example more relatable.

Before:

### Commit message with scope
```
feat(lang): added polish language
```

After:

### Commit message with scope
```
feat(lang): add polish language
```

See #65 for an implementation.

#77 would go further and recommend imperative present tense, rather than just modeling it in this example commit message.

Originally created by @apetro on GitHub (Aug 20, 2018). Originally assigned to: @hutson on GitHub. While Conventional Commits itself does not specify verb voice and tense for the description, it's common to use imperative, present tense describing what the commit, if applied, does, rather than past tense describing what was done. So adopt this convention in the example, making the commit message example more relatable. Before: ### Commit message with scope ``` feat(lang): added polish language ``` After: ### Commit message with scope ``` feat(lang): add polish language ``` See #65 for an implementation. #77 would go further and recommend imperative present tense, rather than just modeling it in this example commit message.

GiteaMirror added the enhancement suggestion labels 2026-02-17 11:37:40 -06:00

GiteaMirror closed this issue

2026-02-17 11:37:41 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#42