From 61d6a28222b0900dc9d1dbab92383d0aee52ef6a Mon Sep 17 00:00:00 2001 From: "coded (Samuel Shuert)" Date: Mon, 6 May 2024 20:03:05 +0000 Subject: [PATCH] docs: update contributing/formatting/projects --- contributing/formatting/projects.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/contributing/formatting/projects.md b/contributing/formatting/projects.md index bf06686..754acc4 100644 --- a/contributing/formatting/projects.md +++ b/contributing/formatting/projects.md @@ -2,7 +2,7 @@ title: Project Standards description: published: true -date: 2024-05-06T02:03:27.122Z +date: 2024-05-06T20:03:03.088Z tags: editor: markdown dateCreated: 2024-05-05T21:22:30.441Z @@ -18,4 +18,9 @@ All projects should provide: - A short summary of what the project does, as well as how to use the project in a top level README.​md - The README should include a badge of who the repository is maintained by - A CONTRIBUTING.​md file top level that tells people how to contribute to said project -- A top level LICENSE file or folder of which includes the License or Licenses used in the project \ No newline at end of file +- A top level LICENSE file or folder of which includes the License or Licenses used in the project + +# Commit Messages +- First line of the commit message should be a short (<50 chars) description of the purpose of the commit + - First word should be one of: `feat:` for feature, `fix:` for bugfixes, or `break:` for breaking changes +- \ No newline at end of file