Martin von Zweigbergk b2e4854a43 docs: explain a bit about good commit messages ... We didn't have any guidelines about what to include in a commit message. Others have already written good guides for that. This commit adds a link to one. I also added a sentence about explaining the reason for a change, since I think that's particularly often missed (I'm sure I also miss it sometimes - don't hesitate to point out when that happens).		2024-10-07 17:02:49 -07:00
..
design
governance
technical
bookmarks.md
cli-reference.md
code-of-conduct.md
community_tools.md
config.md
config.toml
conflicts.md
contributing.md	docs: explain a bit about good commit messages	2024-10-07 17:02:49 -07:00
design_doc_blueprint.md
design_docs.md
FAQ.md
filesets.md
git-comparison.md
git-compatibility.md
github.md
glossary.md
index.md
install-and-setup.md
operation-log.md
related-work.md
revsets.md
roadmap.md
sapling-comparison.md
templates.md
testimonials.md
tutorial.md
windows.md
working-copy.md