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	bookmarks: update docs to try to clarify mapping to Git branches	2024-10-01 06:46:32 -07:00
cli-reference.md
code-of-conduct.md
community_tools.md	docs: add link to VisualJJ	2024-10-05 01:18:52 -07:00
config.md	docs: mention snapshot.auto-track in config.md too	2024-10-04 12:42:22 -07:00
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	docs: update stale references to singular file() revset	2024-10-03 22:39:42 +02:00
roadmap.md
sapling-comparison.md
templates.md
testimonials.md
tutorial.md	unsquash: deprecate in favor of squash and diffedit	2024-09-26 16:34:48 +02:00
windows.md
working-copy.md	docs: mention snapshot.auto-track in config.md too	2024-10-04 12:42:22 -07:00