githubschool / githubschool/corrie
Parking Lot
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Post any questions you may have here during the training.
# Link to [training manual](https://githubtraining.github.io/training-manual/#/01_getting_ready_for_class)
### Day 1
[Day 1 Meeting recording](https://github.zoom.us/rec/share/4NEyDou322pIW5X27G7hfe0zJ9_UX6a81XAZq_AIyRu2raBX1hoFZ8djMsoHmmyr)
Access Password: 5N&808B+
- [x] Intro
- [x] What is Git & GitHub?
- [x] Local operations
- [x] GitHub flow
- [x] Projects
### Day 2
**My apologies - I did not hit record and the mere 10mins recording that I have wasn't very helpful, if you want to practice what we have covered today, you can try and complete the breakout activity again as well as review those bullet points**
- [x] Pull requests
- [x] Closing an issue + Automated Kanban
- [x] Branch Protections
- [x] Tags & Releases
**Breakout Activity**:
- Create an issue
- Add issue to a project board with automated kanban
- Propose a new change using the GitHub Flow
- Use keywords to close out issue
- Have someone approve your work
- Merge into `master` and tag it
- Create a release (Good exercise for test engineers)
- Check progress on project board
**Here are some bullet points to help you review what we have covered:**
- git: Centralized vs. Distributed version control system
- Git vs. GitHub
- What is a repository?
- What is README.md?
- What is Markdown?
- How to unsubscribe from repository / Pull Request / Issues
- What is the GitHub Flow?
- Why do we need Pull Requests?
- Why do we need branch protection?
- What is a draft Pull Request?
- Why do we need to open PR as soon as possible? How do I inform repo managers that my pull request is still a work in progress, so that they don't merge my PR?
### Day 3
[Day 3 Meeting recording](https://github.zoom.us/rec/share/vO0kcvas11lJS7Pdt3OPZfR-LKHEX6a8gykZ-6AJmRl_G6dHfoDHNWIdjdPemOK6)
Access Password: 1d?#?*@U
- [x] Git Basic commands
- [x] Merge Conflicts
- [x] CODEOWNERS
- [ ] Revert
- [ ] Reset
- [x] LFS
### Day 4
[Day 4 Meeting recording]()
**Access Password:**
- [ ] IDE tools: Atom, VSCode, GitHub Desktop
- [x] `.gitignore` [LabVIEW template](https://github.com/github/gitignore/blob/master/LabVIEW.gitignore)
Breakout rooms:
- [ ] Workflow: Putting it all together
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked training manual and the Day 1–4 checklist to understand the training context. This is a general question parking lot rather than a defined change, so completion cannot be verified until a specific documentation request is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, markdown
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100