[x] 🥚 Creating Issues: You can create a new issue in a GitHub repository using an issue template. You can correctly use labels, milestones, and assignments to make your issue findable.
[x] 🥚 Searching Issues: You can find issues in a repository by label, author, and milestone.
[x] 🥚 Project Boards: You can use issues on a GitHub project board to track your class assignments and help your classmates when they need it.
HYF Workflows:
[x] 🥚 Check-Ins: You can use the check-in template to track your module learning objectives, your weekly progress (and to post a retrospective at the end of the module). You create one check-in issue per module in the class repo and each Thursday you add a check-in comment to it and the label for the corresponding week. After review, we add the checked label. No need to remove previous labels either. So as an example, after a 5 week module, you would have 5 comments and 5 labels added by you.
[x] 🥚 Deliverables: You can create an issue for this module's deliverable and track your progress on the class project board. Each week, there are different assignments/deliverables. If it is an individual project, you create your deliverable issue for it in the class repo. If it is a group project, the entire group creates 1 issue together in the class repo.
[x] 🥚 Asking for Help: You can use the help-wanted template in your class repository's Discussion board to ask for help, and to help your classmates when they are blocked.
Your Computer:
[x] 🥚 File System Management: You can create and organize a new folder on your personal computer for the materials you will study at HYF.
Visual Studio Code:
[x] 🥚 Install and manage extensions
[x] 🥚 Open a folder for editing
[x] 🥚 Create new files/folders inside of the folder
[x] 🥚 Edit files and save changes
Week 1
I Need Help With:
Currently No
What went well?
Created Issue
Installed Softwares
What went less well?
Installed nvm
Lessons Learned
install extensions for VS code
create check-in and deliverables issues
Learning Objectives
check-intemplate to track your module learning objectives, your weekly progress (and to post a retrospective at the end of the module). You create one check-in issue per module in the class repo and each Thursday you add a check-in comment to it and the label for the corresponding week. After review, we add the checked label. No need to remove previous labels either. So as an example, after a 5 week module, you would have 5 comments and 5 labels added by you.deliverableand track your progress on the class project board. Each week, there are different assignments/deliverables. If it is an individual project, you create your deliverable issue for it in the class repo. If it is a group project, the entire group creates 1 issue together in the class repo.help-wantedtemplate in your class repository's Discussion board to ask for help, and to help your classmates when they are blocked.Week 1
I Need Help With:
Currently No
What went well?
Created Issue Installed Softwares
What went less well?
Installed nvm
Lessons Learned
install extensions for VS code create check-in and deliverables issues
Sunday Prep Work