1
0
Fork 0
mirror of synced 2024-05-21 05:02:37 +12:00

Removed un-needed titles

This commit is contained in:
Eldad A. Fux 2020-09-23 06:58:36 +03:00 committed by GitHub
parent 47d4dfcc55
commit 0a50f66d08
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -39,31 +39,28 @@ For the initial start, fork the project and use git clone command to do
<br/>
### <strong>A standard procedure for working on an issue would be to: </strong>
### 1. `git pull`, before creating a new branch, pull the changes from upstream. Your master needs to be up to date.
1. `git pull`, before creating a new branch, pull the changes from upstream. Your master needs to be up to date.
```
$ git pull
```
### 2. Create new branch from `master` like: `doc-548-submit-a-pull-request-section-to-contribution-guide`<br/>
2. Create new branch from `master` like: `doc-548-submit-a-pull-request-section-to-contribution-guide`<br/>
```
$ git checkout -b [name_of_your_new_branch]
```
### 3. Work - commit - repeat ( be sure to be in your branch )
<br/>
3. Work - commit - repeat ( be sure to be in your branch )
### 4. Push changes to GitHub
4. Push changes to GitHub
```
$ git push origin [name_of_your_new_branch]
```
<br/>
### 6. Submit your changes for review
6. Submit your changes for review
If you go to your repository on GitHub, you'll see a `Compare & pull request` button. Click on that button.
### 7. Start a Pull Request
7. Start a Pull Request
Now submit the pull request and , click on `Create pull request`.
### 6. Get a code review approval / reject
### 7. After approval, merge your PR
### 8. GitHub will automatically delete the branch, after the merge is done. (they can still be restored).
<br/>
6. Get a code review approval / reject
7. After approval, merge your PR
8. GitHub will automatically delete the branch, after the merge is done. (they can still be restored).
## Setup From Source