From 54cb08b710f911b1268b5a3465bb8781cd7c0c39 Mon Sep 17 00:00:00 2001 From: Ibrahim Abdelkader Date: Sat, 19 Feb 2022 16:59:04 +0200 Subject: [PATCH] Update README.md --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a9ef110ef..d2fed67b7 100644 --- a/README.md +++ b/README.md @@ -108,12 +108,13 @@ git push origin -u Please follow the [best practices](https://developers.google.com/blockly/guides/modify/contribute/write_a_good_pr) when sending pull requests upstream. In general, the pull request should: * Fix one problem. Don't try to tackle multiple issues at once. * Split the changes into logical groups using git commits. -* Pull request title should be < 78 characters, and match this pattern: `: .` -* Commit subject line should be < 78 characters, and match this pattern: `: .` -For example: +* Pull request title should be less than 78 characters, and match this pattern: `:<1 space><.>` +* Commit subject line should be less than 78 characters, and match this pattern: `:<1 space><.>` +Example PR titles or commit subject lines: ``` github: Update workflows. Libtf: Add support for built-in models. -RPC: Remove CAN bit timing function. -OPENMV4: Add readme txt file. +RPC library: Remove CAN bit timing function. +OPENMV4: Add readme template file. +ports/stm32/main.c: Fix storage label. ```