7 Commits

Author	SHA1	Message	Date
omahs	dd0ed0ef17	docs: fix typos in repository documentation (#10683)	2025-11-15 20:22:29 -08:00
Michael Vorburger	2c776f0780	CONTRIBUTING: Explicitly note docs:... as a good example (#11755)	2025-08-09 18:12:30 -07:00
Ruyut	b72e5adb14	CONTRIBUTING: fix typo in commit message example (#11528)	2025-07-25 14:24:06 -07:00
Devon Rifkin	c38680b8a1	CONTRIBUTING: fix code block formatting ... There were only 3 spaces instead of 4, so the example was being considered to include html elements	2025-04-07 13:53:33 -07:00
Blake Mizerany	2099e2d267	CONTRIBUTING: provide clarity on good commit messages, and bad (#9405) ... Also, our commit messages have been getting better, but we can do better, and be more consistent. This adds more clarity on how to write commit messages and provides examples of good and bad messages. Also, our contributing guide was lacking helpful guidance on how to start change proposals. This commit adds the start of that section. Soon, we should add a proposal template to the issue tracker with a link back to the proposal section, which should also be expanded upon.	2025-02-27 19:22:26 -08:00
Carter	369479cc30	docs: fix spelling error (#6391) ... change "dorrect" to "correct"	2024-09-04 09:42:33 -04:00
Jeffrey Morgan	8200c371ae	add CONTRIBUTING.md (#6349)	2024-08-14 15:19:50 -07:00