Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit a900542

Browse files
authored
Update hand-in-homework-guide.md
1 parent d11e835 commit a900542

File tree

1 file changed

+14
-16
lines changed

1 file changed

+14
-16
lines changed

hand-in-homework-guide.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -10,32 +10,30 @@ Follow the walkthrough to learn how to submit your homework for each week:
1010

1111
ONE TIME ONLY (START OF EVERY MODULE)
1212

13-
1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the module repository. You do this by using the `fork` option on GitHub
14-
2. Navigate to the URL of the cloned repository (it should be in your personal account, under "repositories")
15-
3. Clone the repository, using SSH, to your local machine
13+
1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the original module repository. You do this by using the `fork` option on the top right
14+
2. Navigate to the URL of the cloned repository (it should be in your personal GitHub account, under "repositories")
15+
3. Clone the repository, using SSH, to your local machine. You can do this by typing in `git clone <git url>` in the command line
1616
4. On your local machine, navigate to the folder using the command line
17-
5. Make sure you've cloned it correctly by running `git status` from the command line. You should see the following message:
18-
19-
[[ INSERT IMAGE OF HOW TO CHECK CLONE ]]
17+
5. Make sure you've cloned it correctly by running `git status` from the command line.
2018

2119
EVERY WEEK
2220

23-
5. Create a new branch for each week you have homework. For example, for the week 1 homework for JavaScript1 create a branch called `week-1-homework-YOUR_NAME`
24-
6. Make your homework in the right folder, while in this branch
25-
7. Once you're finished, add and commit everything. Make the commit message meaningful, for example `finished project for homework week1`
26-
8. Push the branch to your forked repository
27-
9. On GitHub, click on the `create pull request` button. Make sure the `base repository` is the original, on branch master
28-
10. Give the pull request a title in the following format:
21+
1. Create a new branch for each week you have homework. For example, for the week 1 homework for JavaScript1 create a branch called `week-1-homework-YOUR_NAME`
22+
2. Make your homework in the right folder, while in this branch
23+
3. Once you're finished, add and commit everything. Make the commit message meaningful, for example `finished project for homework week1`
24+
4. Push the branch to your forked repository
25+
5. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is the original, on branch master
26+
6. Give the pull request a title in the following format:
2927

3028
```markdown
31-
js1 homework week 1 noerpaanakker
29+
Homework week 1 <Your name>
3230
```
3331

34-
11. Submit the pull request from your forked repository branch into the `master` branch of the original repository
35-
12. Do a little victory dance because you did it! Good job!
32+
7. Submit the pull request from your forked repository branch into the `master` branch of the original repository
33+
8. Do a little victory dance because you did it! Good job!
3634

3735
For a visual walkthrough the steps please watch the following video one of our teachers, Unmesh Joshi, has made:
3836

39-
- [GitHub Homework flow](https://www.youtube.com/watch?v=2qJPAVTiKPE)
37+
- [GitHub Homework flow](https://www.youtube.com/watch?v=2qJPAVTiKPE)
4038

4139
If you have any questions or if something is not entirely clear ¯\\\_(ツ)\_/¯, please ask/comment on Slack!

0 commit comments

Comments
 (0)