The goal of this course is to give you a brief introduction to Git, SSH, and GitHub. Weโll also provide you with materials for further learning and a few ideas to get you started on our platform. ๐
- Use Git can be used to manage source code (documentation source code)
- Use SSH to access GitHub
- Use HTTPS to access GitHub
- Learn about the rich GitHub ecosystem for software development
- Gain familiarity with GitHub Actions
Please read and understand the background material on Git and GitHub.
Become familiar with Secure Shell (SSH) and how it can be used to access a remote Git repository by reading this documentation.
- Add your "@udayton.edu" email to your GitHub account. It does not need to be your primary email in the account.
- Enable two factor (2FA) on your GitHub account to secure it properly.
- Create your profile README. Let the world know a little bit more about you! What are you interested in learning? What are you working on? What's your favorite hobby? Learn more about creating your profile README in the document, "Managing Your Profile README".
- Create a SSH key pair on your primary computer. Upload the SSH public key to your GitHub.com account. You can obtain anyone's public keys on GitHub via their api. For example, to get the instructor's public key run
curl https://github.com/ktarplee.keys
or browse to it here. Replacektarplee
with your username and ensure you can download your public key(s). - Go to your user dashboard and create a new repository. Experiment with the features within that repository to familiarize yourself with them. Try cloning your repository with HTTPS and with SSH to observe the difference.
- Use Git to clone your repository to your computer.
- Create a new markdown file in this repository called
Expectations.md
at the top level of the repository. In the file please describe your expectations for the course. To get started please answer these questions: What you expect to get out of this course? What you are most looking forward to in the course? Why you are taking the course? There are not wrong answers to this, only incorrect markdown formatting. Please use section headers and bulleted or numbered lists in your writeup. - Use Git to commit and push your changes to GitHub.com so they show up when viewed in a web browser.
- Make sure your markdown file passes the markdown linter. View the GitHub Actions for your assignment to see any errors.
- (Extra Credit) Make at least one signed commit in your assignment. This commit must show up as a "verified" commit on GitHub to receive extra credit. The documentation for signing your commits is here.