Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
format of commit messages
See original GitHub issueI’ve used the #ISSUE_NO: SOME_MESSAGE format like #123: add foo. I think this is good for issue-based developing with only myself, but now many people joined to develop online-judge-tools and the format may become just annoying.
So, I think we should use just simple/free format now.
@fukatani What do you think?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to Write a Git Commit Message - cbea.ms
The seven rules of a great Git commit message · Separate subject from body with a blank line · Limit the subject line...
Read more >How to Write Good Commit Messages: A Practical Git Guide
How to write good commit messages · Separate the subject from the body with a blank line · Your commit message should not...
Read more >Conventional Commits
Commits MUST be prefixed with a type, which consists of a noun, feat , fix , etc., followed by the OPTIONAL scope, OPTIONAL...
Read more >How to Write Good Git Commit Messages | Chiamaka Ikeanyi
7 rules of a great Git commit message · Separate subject from body with a blank line · Limit the subject line to...
Read more >Writing Meaningful Commit Messages - Reflectoring
The Angular commit message format is another conventional format. It suggests that a commit message should consist of a header, a body, and...
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 Free
Top 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
Okay, let’s stop using the old format.
I agree with you.
As long as PR-base development continues, every time we merge PR, commit massage like “Merge pull request #562 from pieceofeden/translate-Japanese-documents-to-English-#530” is generated automatically. Since this message include PR number, we only have to correspond PR to issue.
Doing the tedious work manually is easy to omit or mistake. This problem can be solved by automation.
I think that any format is unnecessary.