Reddit Tech VN BotMở source file cấu hình Vim dưới 30 dòng giúp viết commit message chuẩn: giới hạn 50 ký tự cho tiêu đề, xuống dòng trống, body tự xuống dòng ở 72 ký tự, kiểm tra chính tả. Dễ cài đặt, phù hợp ai dùng Git + Vim. Có thể tùy chỉnh theo Conventional Commits. #Git #Vim #OpenSource #CommitMessage #LậpTrình #CôngCụ #DevTool
ferricoxideA lot of my co-workers use graphical code-editors — mostly VScode but occasionally editing straight in #GitHub or #GitLab — or even full-fledged #IDEs. Seems like very few of those tools enforce useful #CommitMessage. When I'm writing commit-messages — be they individual commits or part of a merge-commit — I'm trying to leave a "here's what I did and why" documentation-trail. Even if someone is competent at reading code, a good commit message can help with more-quickly understanding what's going on (especially if, like me, you're working across projects, across code-bases and across languages and/or frameworks).
#git
#git
HaraldGit commit messages: do you use plain text or rather consciously markdown?
1. Reasons for plain text: Commit messages are not always viewed with tools which render markdown, and those which render markdown ... render which markdown exactly?
2. Reasons for markdown: most markdown constructs are meanwhile known to developers, so it improves readability even without rendering.
#git #gitlab #githib #codeberg #forgejo #markdown #commitmessage
plain text
markdown
other funky format (describe in a comment)
Poll ended at .
PHP ZenStill writing “WIP” or “Fix stuff” in your commits?
🔹 A good commit = clear + useful + readable
🔹 Future-you will thank you
📌 7 simple rules to follow
🔗https://levelup.gitconnected.com/good-commit-vs-your-commit-how-to-write-a-perfect-git-commit-message-6e96ab6357fa
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸#proTip: When you open a file of #code to edit it, fill in the #commitMessage with the goal of the changes you want to make in your #versionControl interface.
After you make your changes, only "Add" the changes necessary to accomplish the goal in the commit message; anything else should go in a separate #commit.
This keeps you focused on the task, and prevents your #commits from getting polluted with unrelated work that may confuse #codeReview.
Matt WiebeRestore the vendor lint honeypot #commitmessage
sungsphinx
Hayden StainsbyIn which I try to convince the reader that commit messages are really the best store of information about changes to code and they should be made better use of.
musicmatze 
#git #commitmessage of the day:
The only situation where less spaghetti is better is in programming!
abs(in)thePin wins #pkgsrc #commitMessage so far of 2024:
https://mail-index.netbsd.org/pkgsrc-changes/2024/01/26/msg291797.html