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

Skip to content

Commit 384bfc1

Browse files
authored
Update hand-in-homework-guide.md
1 parent 37d74c1 commit 384bfc1

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

hand-in-homework-guide.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ ONE TIME ONLY (START OF EVERY MODULE)
2020

2121
EVERY WEEK
2222

23-
1. Create a new branch for each week you have homework. For example, for the week 1 homework for JavaScript2 create a branch called `week-1-homework-YOUR_NAME`
24-
2. Inside the correct week folder, create another folder called `homework`. Make your homework files in there, while on the correct branch
23+
1. Create a new branch for each week you have homework. For example, for the week 1 homework create a branch called `YOUR_NAME-w1`
24+
2. Inside the correct week folder, create another folder called `homework` if it is not there yet. Make your homework files in there, while on the correct branch
2525
3. Once you're finished, add and commit everything. Make the commit message meaningful, for example `finished project for homework week1`
2626
4. Push the branch to your forked repository
2727
5. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is your teacher's repository, on branch master
@@ -34,8 +34,4 @@ Homework week 1 <Your name>
3434
7. Submit the pull request from your forked repository branch into the `master` branch
3535
8. Do a little victory dance because you did it! Good job!
3636

37-
For a visual walkthrough the steps please watch the following video one of our teachers, Unmesh Joshi, has made:
38-
39-
- [GitHub Homework flow](https://www.youtube.com/watch?v=2qJPAVTiKPE)
40-
4137
If you have any questions or if something is not entirely clear ¯\\\_(ツ)\_/¯, please ask/comment on Slack!

0 commit comments

Comments
 (0)