Skip to content
This repository was archived by the owner on Sep 11, 2024. It is now read-only.

Commit b55e07e

Browse files
authored
Merge pull request #49 from AkshayaKulasekaran/patch-2
Improving Readability
2 parents 62ccd92 + 6b2b8e3 commit b55e07e

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

NEWCOMERS.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# GIT CONTRIBUTION FLOW
2-
To make changes to a repository, follow these steps;
2+
To make changes to a repository, follow these steps:
33

4-
# Fork The Repository
5-
- On the top right, click on the fork button, a copy of the repository would be created on your github account, this would take few seconds to get completed.
6-
- Once this is done, click on the green clone drop-down by the top left and copy the url you see, you would use this later.
4+
## Fork The Repository
5+
- On the top right, click on the fork button. A copy of the repository would be created on your github account - this will take few seconds
6+
- Once this is done, click on the green clone drop-down by the top left and copy the url you see. You will use this later
77

8-
# Clone your fork to your local machine
8+
## Clone your fork to your local machine
99
This simply means getting a copy of the repository on your personal computer.
1010
On your computer terminal, cd into the directory you want to clone the repo to.
1111
```
@@ -16,13 +16,13 @@ now, enter this,
1616
git clone "paste the url you copied here"
1717
```
1818

19-
# Create a Branch
20-
To work on a new feature or fix a bug, it's important that you create a new branch. this keeps your changes seperate from the master branch for easy management of multiple pull requests for each completed task.
21-
Enter this
19+
## Create a Branch
20+
To work on a new feature or fix a bug, it's important that you create a new branch. This keeps your changes seperate from the master branch for easy management of multiple pull requests for each completed task.
21+
Enter this,
2222
```
2323
git checkout master
2424
```
25-
Create a branch with a name
25+
Create a branch with a name of your choice,
2626
```
2727
git branch "your-branch-name"
2828
```
@@ -32,26 +32,26 @@ git branch "your-branch-name"
3232
git checkout "your-branch-name"
3333
```
3434

35-
Now you can go ahead and affect the desired changes.
35+
Now you can go ahead and affect the desired changes
3636

37-
## Submitting your changes (a Pull Request)
38-
on your terminal, Enter this to check the modified files
37+
## Pushing your changes
38+
Enter this to check the modified files on your terminal,
3939
```
4040
git status
4141
```
4242
To add the changes,
4343
```
4444
git add .
4545
```
46-
Commit your changes
46+
Commit your changes,
4747
```
4848
git commit -m "Add-a-commit-message-here"
4949
```
5050
Now, you can push your changes to the branch you created
5151
```
5252
git push origin "your-branch-name"
5353
```
54-
# Submitting
54+
## Submission - A Pull Request (PR)
5555
Once you've committed and pushed all of your changes to GitHub, reload the page for your fork on GitHub, select your branch, and click the green compare and pull request button by the top right, add a description and the number for the issue your pull request and submit.
5656

5757

0 commit comments

Comments
 (0)