Home

Welcome to the git-github-zero-to-hero wiki! This wiki is used for capturing notes and tips for the delivery of this course.

Instructor Tips

Small screen teaching, share screen with chrome window and gtikraken.
Large screen Blackboard collaborate, ensuring I can see emoji status updates, on one window and course materials on another.

Command Palette: When creating new files, ensure you leave the path up long enough. Request feedback.
Before beginning working on issue, ensure all team members have found their issue and are looking at it.
Issue with accepting (finding) GitHub invitations: https://github.community/t/where-do-i-see-all-incoming-invitations-collaborator/661/4.
- Solution: You can also see the invite if you know which repo you were invited to: https://github.com/username/reponame/invitations
Issues with GitKraken on UBUNTU: installation issue: Solution add note to setup instructions about testing UBUNTU especially and getting in touch if they have issues before course. Appearance issue (not sure what this is?)

As a moderator/instructor, join the session through https://vle.shef.ac.uk/ > Organisations > Research Software Engineering > find the day's session and join.
When asking for yes/no responses on recording the session, use a poll to more easily see who a response is needed from.
Use emoji responses (or chat) for assessing whether participants are following. Use raised hands for critical problems that might need assistance.

stress that git is a piece of software on your computer; GitHub is a website/platform
Stop for questions periodically - after git & GitHub, before GitKraken client
Licenses
- Code and other types of content (e.g. photos) have different sorts of license (e.g. CC-BY)
Might be worth noting that "repositories" are a git concept, as well as the way that they are presented on GitHub.

Before this section, and before the break, check that everyone is set up and has their SSH key (or whatever) authentication set up.