Skip to content

Commit f8664d7

Browse files
authored
Merge pull request #22 from CodeYourFuture/update-review-guides
Update review and help guidance markdowns
2 parents 3663a5f + 13e8622 commit f8664d7

File tree

3 files changed

+123
-0
lines changed

3 files changed

+123
-0
lines changed

.github/pull_request_template.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
<!--
2+
3+
You must title your PR like this:
4+
5+
COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
6+
7+
For example,
8+
9+
NW4 | Carol Owen | HTML-CSS-Module | Week1
10+
11+
Complete the task list below this message.
12+
If your PR is rejected, check the task list.
13+
14+
-->
15+
16+
## Learners, PR Template
17+
18+
Self checklist
19+
20+
- [ ] I have committed my files one by one, on purpose, and for a reason
21+
- [ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
22+
- [ ] I have tested my changes
23+
- [ ] My changes follow the [style guide](https://syllabus.codeyourfuture.io/guides/code-style-guide/)
24+
- [ ] My changes meet the [requirements](./README.md) of this task
25+
26+
## Changelist
27+
28+
Briefly explain your PR.
29+
30+
## Questions
31+
32+
Ask any questions you have for your reviewer.

HOW_TO_REVIEW.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
<!--
2+
Do not edit this file.
3+
Make a change to the template and then pull changes
4+
Repo: https://github.com/CodeYourFuture/Module-Template
5+
-->
6+
7+
# Everyone reviews code at CYF
8+
9+
Mentors and trainees all review code, and collaborate on improving code quality. We are all helping each other to talk, write, and think about code more clearly.
10+
11+
We are not reviewing code as if we were to merge this PR into production; we are opening a technical conversation for the purpose of insight and development.
12+
13+
## Key points:
14+
15+
1. Ask questions instead of making statements:
16+
17+
**YES:** "Is there another element you could use to group a set of fields in a form? Why might someone use a different element in a form?"
18+
**NO:** "Use fieldset not divs"
19+
20+
2. Encourage simplicity, clarity, and precision:
21+
22+
**YES** "There are 15,0000 files in this changelist. Which files should be reviewed?"
23+
**NO** "It doesn't matter; I can try to figure out what you meant."
24+
25+
3. Respect everyone's work and time:
26+
27+
**YES** "I think there's some more to do here. Thanks for sharing where you're up to."
28+
**NO** "This is rubbish. Try harder."
29+
30+
## Labels
31+
32+
Reviewers, please add labels (provided) to the PR once you've reviewed. This helps to focus the trainee on the areas they should work on, and gives an overview for mentors on what the whole cohort needs to work on.
33+
34+
## Solutions
35+
36+
### Where to find solutions?
37+
38+
You can find the solutions for the module on the `solutions` branch.
39+
40+
### Solutions branch
41+
42+
The solutions branch typically contains:
43+
44+
#### Sample solutions
45+
46+
Solutions are example answers not the only correct answers.
47+
48+
#### Common responses guides.
49+
50+
Everyone is invited to contribute commonly encountered problems, mistakes, misunderstandings, and mental-model errors to our common responses documents.
51+
52+
Use these resources to inform your code review, get unstuck, and improve your understanding.
53+
54+
## Guides
55+
56+
Here's a detailed checklist of the sorts of things we should check code for:
57+
58+
https://syllabus.codeyourfuture.io/guides/marking-guide
59+
60+
Here's a detailed style guide to help us all write clear, high quality code:
61+
62+
https://syllabus.codeyourfuture.io/guides/code-style-guide
63+
64+
Here's some help with giving good feedback during code review:
65+
66+
https://teachertraining.codeyourfuture.io/tasks/code-review

contributing.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
<!--
2+
Do not edit this file.
3+
Make a change to the template and then pull changes
4+
Repo: https://github.com/CodeYourFuture/Module-Template
5+
-->
6+
7+
# How To Submit Your Coursework
8+
9+
Use Git & Github to submit your coursework as a pull request.
10+
11+
The Github Desktop cheatsheet will help you.
12+
13+
[Github Desktop Cheatsheet](http://syllabus.codeyourfuture.io/git/cheatsheet)
14+
15+
This module will help you submit your coursework.
16+
17+
[Git](http://syllabus.codeyourfuture.io/git/index)
18+
19+
## Questions & Help
20+
21+
Contributing to a remote codebase is a necessary skill for a professional developer. Opening PRs is mandatory at CYF. It is part of the coursework.
22+
23+
If you cannot submit your coursework you **must** post on Slack to get unblocked.
24+
25+
[How to get help](./HOW-TO-GET-HELP.md)

0 commit comments

Comments
 (0)