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

Skip to content

Commit 4936555

Browse files
authored
Update hand-in-homework-guide.md
1 parent 2b69707 commit 4936555

File tree

1 file changed

+21
-21
lines changed

1 file changed

+21
-21
lines changed

hand-in-homework-guide.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,37 @@
1-
# How to hand in homework
1+
# How to hand in the weekly assignment
22

3-
In this module you'll submit your homework only using GIT and GitHub.
3+
In this module you'll submit your assignment only using GIT and GitHub.
44

55
1. [GitHub](https://www.github.com/HackYourFuture/JavaScript)
66

7-
## 1. GitHub homework guide
7+
## 1. GitHub assignment guide
88

99
<a href="http://www.youtube.com/watch?feature=player_embedded&v=CpYARPYGQU8" target="_blank"><img src="./assets/submit-homework.png" width="400" height="250" alt="HYF Video" /></a>
1010

11-
Watch the video (by clicking the image) or go through the following walk-through to learn how to submit your homework:
11+
Watch the video (by clicking the image) or go through the following walk-through to learn how to submit your assignment:
1212

1313
ONE TIME ONLY (START OF EVERY MODULE)
1414

15-
1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the homework module repository. For JavaScript (as well as the next 2 modules), the homework module repository is `https://www.github.com/HackYourHomework/Homework-classXX` where XX is your class number. You do this by using the `fork` option on the top right.
15+
1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the assignment module repository. For JavaScript (as well as the next 2 modules), the assignment module repository is `https://www.github.com/HackYourHomework/Assignment-cohortXX` where XX is your cohort number. You do this by using the `fork` option on the top right.
1616
2. Navigate to the URL of the cloned repository (it should be in your personal GitHub account, under "repositories").
1717
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.
1818
4. On your local machine, navigate to the folder using the command line.
1919
5. Make sure you've cloned it correctly by running `git status` from the command line.
20-
6. This homework repository is a little special, have a look through the README how it all works!
20+
6. This assignment repository is a little special, have a look through the README how it all works!
2121

2222
EVERY WEEK
2323

2424
1. Do a `git pull` on your main branch to get the latest version.
25-
2. Create a new branch for each week you have homework. For example, for the week 3 homework² for JavaScript create a branch called `YOUR_NAME-w3-JavaScript`. Don't forget to checkout this branch after creating it. You should not modify the `main` branch.
26-
3. Make your homework!
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!
28-
5. Create the commit (`git commit`). Make the commit message meaningful, for example `Finished project for homework week 3`.
25+
2. Create a new branch for each week you have assignment. For example, for the assignment week 3² for JavaScript create a branch called `YOUR_NAME-w3-JavaScript`. Don't forget to checkout this branch after creating it. You should not modify the `main` branch.
26+
3. Make your assignment!
27+
4. Once you're finished, add your assignment to a commit. There will be some test and config files added by the test runner, this is expected and should be added!
28+
5. Create the commit (`git commit`). Make the commit message meaningful, for example `Finished project for assignment week 3`.
2929
6. Push the branch to your forked repository.
30-
7. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is the `Homework-classXX` repository, on branch `main`.
30+
7. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is the `Assignment-cohortXX` repository, on branch `main`.
3131
8. Give the pull request a title in the following format:
3232

3333
```markdown
34-
Homework week 3 <Your name>
34+
Assignment week 3 <Your name>
3535
```
3636

3737
9. Submit the pull request from your forked repository branch into the `main` branch.
@@ -41,16 +41,16 @@ If you have any questions or if something is not entirely clear ¯\\\_(ツ)\_/¯
4141
Notes:
4242

4343
1. If you are in an AZC you may need to use HTTPS instead as the AZC may have blocked the network protocol used by SSH.
44-
2. This first week for which you need to submit homework is week 3 of the JavaScript module.
44+
2. This first week for which you need to submit assignment is week 3 of the JavaScript module.
4545

46-
# Homework Review Process
46+
# Assignments Review Process
4747

4848
## Before you start
4949
1. You get assigned a mentor at the start of the module in the slack group chat. (S)He is responsible for reviewing your work for the duration of the module.
50-
3. Please don't hesitate to contact Tjebbe or the class mentor if you are facing any issues. We are here to help you out!
50+
3. Please don't hesitate to contact Joséphine or the cohort supervisor if you are facing any issues. We are here to help you out!
5151

5252
## Review process
53-
Together with the mentor and other students in your group you have the freedom to decide on the way of communication. You can do video calls or get feedback via comments to the PR.
53+
Together with the mentor and other trainees in your group you have the freedom to decide on the way of communication. You can do video calls or get feedback via comments to the PR.
5454

5555
The mentor will start a group message on Slack and agree together on the way of communication. There, the mentor can keep the whole group informed of his/her availability and updates.
5656

@@ -68,19 +68,19 @@ The mentor will place comments on your pull request. You have to adjust your wor
6868
| --- | --- |
6969
|Tuesday (week 1) | Deadline for you to hand in your first version |
7070
|Wednesday (week 1) - Tuesday (week 2) | Mentor provides feedback |
71-
| Wednesday (week 2) - Tuesday (week 3) | you improve homework based on the feedback and mentor evaluates improvements |
72-
| Wednesday (week 3) | Core-team member Homework Approval Check. At this point every PR needs to be approved. |
71+
| Wednesday (week 2) - Tuesday (week 3) | you improve the assignment based on the feedback and mentor evaluates improvements |
72+
| Wednesday (week 3) | Core-team member Assignment Approval Check. At this point every PR needs to be approved. |
7373

74-
It can happen that your mentor doesn't reply on your questions or your updated homework. Please send a reminder via slack. If that doesn't work and you're afraid you can't make the deadline, contact your class-mentor.
74+
It can happen that your mentor doesn't reply on your questions or your updated assignment. Please send a reminder via slack. If that doesn't work and you're afraid you can't make the deadline, contact your cohort supervisor.
7575

7676
### Labels
77-
It is important for the you and the core-team to have up to date info about the status of the homework. This is why the mentors use two labels on your PR.
77+
It is important for the you and the core-team to have up to date info about the status of the assignment. This is why the mentors use two labels on your PR.
7878

7979
| Label | Description |
8080
| --- | --- |
8181
|no label |not reviewed yet |
8282
|Needs work |reviewed, but you need to implement feedback |
83-
|Approved |reviewed, and your homework has been approved |
83+
|Approved |reviewed, and your assignment has been approved |
8484

8585
Here is an example of this in action.
8686

0 commit comments

Comments
 (0)