From a04b5e868fd8dea662e72cda9dfe1a4b06ad2853 Mon Sep 17 00:00:00 2001 From: Steph Piper Date: Tue, 25 Feb 2025 11:03:56 +1000 Subject: [PATCH] Updated How to Contribute to this Project (markdown) --- How-to-Contribute-to-this-Project.md | 1 + 1 file changed, 1 insertion(+) diff --git a/How-to-Contribute-to-this-Project.md b/How-to-Contribute-to-this-Project.md index 76997dc..335e24c 100644 --- a/How-to-Contribute-to-this-Project.md +++ b/How-to-Contribute-to-this-Project.md @@ -72,6 +72,7 @@ Peer reviewers must be an expert in the skill area and contribute detailed feedb * Ordered correctly from basics at the base to advanced at the top * Weaker tiles that could be swapped for stronger tiles * If a skill tree is broad in topic, it is fine for it to have tiles that are in duplicate to subdisciplines in that topic. For example, if both the Sports & Fitness and Running Skill trees have a 'Run 2kms' tile, this is fine. +* Consider using the [changelog](https://keepachangelog.com/en/1.0.0/) system to document your changes, including headings for 'Added', 'Changed' and 'Removed' with info on the decision. Peer reviewers may contribute this feedback as an issue or pull request with a fixed .svg in Github with 'Peer review' in the title. Peer reviewers can receive a contributor sticker in the mail if they wish. If a skill tree has been peer reviewed twice, it is now ready for translation and indicates a high level of confidence in the content.