From 4790540b39b40c60bbc702f282416aed82f311fb Mon Sep 17 00:00:00 2001
From: LostNeophyte <lostneophyte@tuta.io>
Date: Tue, 22 Nov 2022 16:28:40 +0100
Subject: docs: github pull request template update (#3512)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* docs: github pull request template update

* fix: docs

as suggested by @lostneophyte

Co-authored-by: LostNeophyte <lostneophyte@tuta.io>

* chore: fix my(LostNeophyte) mistakes

Co-authored-by: Daniel Rodríguez Rivero <rdanielo@gmail.com>
---
 .github/pull_request_template.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 48782e51..c85733ff 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,10 +1,12 @@
 <!-- This won't be rendered!
 [CHECKLIST]
 I prefixed the title with one of the following tags:
- - feature: for feature addition / improvements
+ - feat: for feature addition / improvements
  - fix: when fixing a functionality
  - refactor: when moving code without adding any functionality
- - doc: on documentation updates
+ - docs: on documentation updates
+
+Aditionally you can specify the scope of the PR in parenthesis, ex `fix(cmp):` or `feat(which-key):` or `docs(readme):`
 
 - I read the contributing guide [CONTRIBUTING.md](../CONTRIBUTING.md)
 - My code follows the style guidelines of this project
-- 
cgit v1.2.3