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

Skip to content

Commit 338d060

Browse files
authored
Update hand-in-homework-guide.md
1 parent a7668a2 commit 338d060

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

hand-in-homework-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ EVERY WEEK
2424
1. Do a `git pull` on your main branch to get the latest version.
2525
2. Create a new branch for each week you have homework. For example, for the week 1 homework for JavaScript create a branch called `YOUR_NAME-w1-JavaScript`. Don't forget to checkout this branch after creating it.
2626
3. Make your homework!
27-
4. Once you're finished, add your homework to a commit. Make sure you *only* commit your homework files and nothing else. You can use `git add -p` if you only want to add a couple files. You can always check what is happening with the `git status` command (as one of our mentors always says, it is the console.log of git!).
27+
4. Once you're finished, add your homework to a commit. There will be some test and config files added by the test runner, this is expected and should be added!
2828
5. Create the commit (`git commit`). Make the commit message meaningful, for example `finished project for homework week1`.
2929
6. Push the branch to your forked repository
3030
7. 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

0 commit comments

Comments
 (0)