#commitmessage — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #commitmessage, aggregated by home.social.
-
Mở 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
-
Git 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
-
Git 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
-
Git 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
-
Git 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
-
Git 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
-
#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.
-
-
In 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.
-
#git #commitmessage of the day:
The only situation where less spaghetti is better is in programming!
-
-
Funny, I actually have a blog article laying around about the topic of writing good commit messages, but I have to say: this is probably the best example out there:
https://dhwthompson.com/2019/my-favourite-git-commit
Nothing to add. Better than anything I could come up with. Love it!
