-
Notifications
You must be signed in to change notification settings - Fork 8
Add contents to QA README files #233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add contents to QA README files #233
Conversation
|
Hey @GayathriVenkatraman thanks for submitting this! I will help guide you as we merge this content into the program. Right now, the linting is failing. You can see that by clicking on the check above, or by running it locally (run "npm install" and then "./lint" to see the errors. Some things can be fixed automtically by running "./lint --fix". These checks have to pass before we merge it to main. You have two options:
It's up to you, which approach sounds best. After the content is ready, we will publish it to program.hackyourfuture.dk. This is the website that we share and teach from (it looks a lot nicer than just showing it on github :D) If you have any questions, feel free to reach out on slack if you ever need anything! |
|
Hey @adamblanchard I've now updated the Lint fix, and it is passing in my local. I've also updated the README.md for further modules and weeks. Let me know if there is any other thing that I should update |
adamblanchard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In our program, we have three files inside each week:
- Preparation - things the trainee should do before the session. Like reading material or small set up tasks.
- Session plan - this contains the actual content for the session, that a mentor/teacher can use to run the session (slides, exercises, etc.)
- Assignment - The "homework" after the session, with any tasks the trainee should complete in the week
Does the QA track follow the same structure? If so, are you planning on adding that content in here too? If it doesn't follow the same structure, maybe you can explain it to me and i can help make a plan for how to put it in here :-) (We can do this in another PR, either way).
No description provided.