From d851733f6afa96f061e5d206c5fef50457883513 Mon Sep 17 00:00:00 2001 From: Krishna Agarwal Date: Thu, 6 Oct 2022 09:01:31 +0530 Subject: [PATCH] fixed typos, removed space --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1e3c4ce91..9ade99cb1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,7 +12,7 @@ Help us keep Appwrite open and inclusive. Please read and follow our [Code of Co ## Submit a Pull Request 🚀 -Branch naming convention is as following +Branch naming convention is as follows `TYPE-ISSUE_ID-DESCRIPTION` @@ -30,7 +30,7 @@ When `TYPE` can be: - **fix** - a bug fix - **refactor** - code change that neither fixes a bug nor adds a feature -**All PRs must include a commit message with the changes description!** +**All PRs must include a commit message with the a description of the changes!** For the initial start, fork the project and use git clone command to download the repository to your computer. A standard procedure for working on an issue would be to: @@ -48,7 +48,7 @@ $ git checkout -b [name_of_your_new_branch] 3. Work - commit - repeat ( be sure to be in your branch ) -4. Before you push your changes, make sure your code follows the `PSR12` coding standards , which is the standard Appwrite follows currently. You can easily do this by running the formatter. +4. Before you push your changes, make sure your code follows the `PSR12` coding standards, which is the standard Appwrite follows currently. You can easily do this by running the formatter. ```bash composer format @@ -60,7 +60,7 @@ Now, go a step further by running the linter by the following command to manuall composer lint ``` -This will give you a list of errors for you to rectify , if there is an instance you need more information on the errors being displayed you can pass in additional command line arguments. More list of available arguments can be found [here](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage). A very useful command line argument is `--report=diff`. This will give you the expected changes by the linter for easy fixing of formatting issues. +This will give you a list of errors for you to rectify, if there is an instance you need more information on the errors being displayed you can pass in additional command line arguments. More list of available arguments can be found [here](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage). A very useful command line argument is `--report=diff`. This will give you the expected changes by the linter for easy fixing of formatting issues. ```bash composer lint --report=diff @@ -116,7 +116,7 @@ After finishing the installation process, you can start writing and editing code #### Advanced Topics -We love to create issues that are good for beginners and label them as `good first issue` or `hacktoberfest`, but some more advanced topics might require extra knowledge. Below is a list of links you can use to learn more about some of the more advance topics that will help you master the Appwrite codebase. +We love to create issues that are good for beginners and label them as `good first issue` or `hacktoberfest`, but some more advanced topics might require extra knowledge. Below is a list of links you can use to learn more about some of the more advanced topics that will help you master the Appwrite codebase. ##### Tools and Libs