PluginStats
Git Commit Message Format downloads statistics
By fobgochod · JetBrains Marketplace · VCS
Create a commit message with the following template. Click birdie or press Alt + Q open formatter dialogClick outside or press Alt + Enter to be completed Commit...
Git Commit Message Format has 19,435 recorded downloads on JetBrains Marketplace.
It ranks #2178 of 2,500 tracked JetBrains Marketplace listings by downloads.
It is rated 4.7 out of 5 from 3 ratings.
PluginStats has 3 daily observations since Oct 16, 2026; the latest is from Oct 18, 2026.
Rating: 4.67 / 5 from 3 ratings
About Git Commit Message Format
Create a commit message with the following template.
• Click birdie or press Alt + Q open formatter dialog • Click outside or press Alt + Enter to be completed
Commit Message Format
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject> <BLANK LINE> <body> <BLANK LINE> <footer>
The header is mandatory and the scope of the header is optional.
Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
Revert
If the commit reverts a previous commit, it should begin with revert: , followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the SHA of the commit being reverted.
Type
Must be one of the following:
• feat: A new feature • fix: A bug fix • docs: Documentation only changes • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) • refactor: A code change that neither fixes a bug nor adds a feature • perf: A code change that improves performance • test: Adding missing or correcting existing tests • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Scope
The scope could be anything specifying place of the commit change. For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc...
You can use * when the change affects more than a single scope.
Subject
The subject contains succinct description of the change:
• use the imperative, present tense: "change" not "changed" nor "changes" • don't capitalize first letter • no dot (.) at the end
Body
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
Footer
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit closes.
Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.
A detailed explanation can be found in this document.
Description from the JetBrains Marketplace listing.
- VCS
Where Git Commit Message Format sits in the listing
Each band is one page of 20. Downloads on a log scale. Placement is projected from downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Ranking history
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (3)Similar JetBrains Marketplace VCS plugins
Data source
Cumulative download counts come from the public JetBrains Marketplace API. JetBrains reports downloads, not active installs. Ratings are the mean of public votes.
Listing: https://plugins.jetbrains.com/plugin/20935-git-commit-message-format. First seen Oct 16, 2026; last successful collection Oct 18, 2026. See the methodology.