[PR #19] [MERGED] fix(example): present tense imperative. "adds ability" -> "add ability". #246

New Issue

GiteaMirror · 2026-02-17T11:55:44-06:00

GiteaMirror commented

2026-02-17 11:55:44 -06:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/19
Author: @apetro
Created: 8/28/2017
Status: ✅ Merged
Merged: 8/28/2017
Merged by: @stevemao

Base: master ← Head: present-tense-imperative-mood

📝 Commits (1)

cfe269e fix(example): present tense imperative. "adds ability" -> "add ability".

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 index.md (+1 -1)

📄 Description

Use the present tense imperative mood in the example commit message.

So, feat(parser): add ability to parse arrays , not feat(parser): adds ability to parse arrays.

Conventional Commits may not need to specify present tense, imperative mood for verbs. But I think at least the example should use the common present tense, imperative mood practice.

Maybe Conventional Commits should specify. Makes for a stronger convention.

References:

Commit Verbs 101: why I like to use this and why you should also like it.: "Always use the verbs in Imperative Present tense. Don’t use Past or Present Continuous tenses for commits."
Git book on commit message recommendations: "It’s also a good idea to use the imperative present tense in these messages. In other words, use commands. Instead of I added tests for or Adding tests for, use Add tests for."
How to Write a Git Commit Message: "Use the imperative mood in the subject line"

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/conventional-commits/conventionalcommits.org/pull/19 **Author:** [@apetro](https://github.com/apetro) **Created:** 8/28/2017 **Status:** ✅ Merged **Merged:** 8/28/2017 **Merged by:** [@stevemao](https://github.com/stevemao) **Base:** `master` ← **Head:** `present-tense-imperative-mood` --- ### 📝 Commits (1) - [`cfe269e`](https://github.com/conventional-commits/conventionalcommits.org/commit/cfe269ec9536e7b0e8bf21c80ef0bed34fd73f3a) fix(example): present tense imperative. "adds ability" -> "add ability". ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `index.md` (+1 -1) </details> ### 📄 Description Use the present tense imperative mood in the example commit message. So, `feat(parser): add ability to parse arrays` , not `feat(parser): adds ability to parse arrays`. Conventional Commits may not need to specify present tense, imperative mood for verbs. But I think at least the example should use the common present tense, imperative mood practice. Maybe Conventional Commits should specify. Makes for a stronger convention. References: + [Commit Verbs 101: why I like to use this and why you should also like it.][]: "Always use the verbs in Imperative Present tense. Don’t use Past or Present Continuous tenses for commits." + [Git book on commit message recommendations][]: "It’s also a good idea to use the imperative present tense in these messages. In other words, use commands. Instead of `I added tests for` or `Adding tests for,` use `Add tests for.`" + [How to Write a Git Commit Message][]: "Use the imperative mood in the subject line" [ Commit Verbs 101: why I like to use this and why you should also like it.]: https://medium.com/@danielfeelfine/commit-verbs-101-why-i-like-to-use-this-and-why-you-should-also-like-it-d3ed2689ef70 [Git book on commit message recommendations]: https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project [How to Write a Git Commit Message]: https://chris.beams.io/posts/git-commit/ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-02-17 11:55:44 -06:00

GiteaMirror closed this issue

2026-02-17 11:55:45 -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#246