Feature request: support commit description
See original GitHub issueIn usual git commit
:
$ git commit -m 'chore(release): v0.0.0-development' -m '[skip ci]'
it will produce
$ git log --format=%s%b -n 1
chore(release): v0.0.0-development
[skip ci]
However, in standard-version
:
$ standard-version -m 'chore(release): %s' -m '[skip ci]'
produce
$ git log --format=%s%b -n 1
chore(release): 0.0.0-development,[skip ci]
Environment
standard-version --version
4.4.0
node --version
v10.14.1
npm --version
6.6.0
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Feature Request Template: How to Manage Suggestions at ...
A feature request is a user's attempt at coming up with a solution to a problem they encountered while using your product. As...
Read more >Commit message templates - GitLab Docs
GitLab uses commit templates to create default messages for specific types of commits. These templates encourage commit messages to follow a particular ...
Read more >How to Write Better Git Commit Messages – A Step-By-Step ...
The Git commit message is a prime example of this. ... Imperative mood gives the tone you are giving an order or request....
Read more >Conventional Commits
A specification for adding human and machine readable meaning to commit messages.
Read more >Better Commit Policy for Jira Server/Data Center
Ideas and requests for new features. Suggest ideas. Vote for the best. See what's planned. Verify the "from branch" when starting a new...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For customisation, you can always use conventional-changelog directly. For adding features to standard-version, it needs to be useful for many users as it’s meant to be an opinionated wrapper with minimal configurations required. I may not fully understand your issue here but I think you can also configure commitlint to fit what you need. I don’t see editing your existing commit in this project fits the scope here.
The body of a commit is usually very long. Hence we only list short descriptions. You can always click the hash to visit the commit page and see details.