code-differently-24-q4

Lesson 00 - Developer Workflow: Git Fundamentals (Slides)

Slides

Pre-work

Please review the following resources before lecture:

Required

• Git + GitHub Branches, Forks, and Pull Requests (Video)
• A Simplified Convention for Naming Branches and Commits in Git

Recommended

• The Git Fork-Branch-Pull Workflow

Homework

• Create a personal README and submit via GitHub.
• Do pre-work for lesson 01.

Personal README

A personal README is a way to teach others how to best work with you. It is useful for expressing your learning style and personal preferences, likes and dislikes.

For this exercise, you with use the MARKDOWN language (the language used to author this very README) to create your own personal version. Your version should incorporate at least one picture, one list, appropriate headings, and be at least 300 words.

For inspiration, feel free to check out the examples at Kaeti’s repo or do your own thing. Have fun, but keep it professional!

Submitting your assignment

To submit your assignment, please do the following:

1. Fork this repository (repo) under your own Github account.
2. In your forked repo, create a new branch and give it a name.
3. Add your README.md and accompanying picture files to a sub-folder you create under lesson_00 (see lesson_00/anthonymays for example).
4. Commit as many changes as you need to your branch and push to Github.
5. When ready to merge, visit this repo to create a pull request (PR).
6. Add details to the PR and create it.

If you need more help, you can check out this page here or watch this YouTube video.

Note: If you would rather not have this README published publicly, please indicate that in your PR description and I will review it without accepting it for merge. The PR can be deleted when done. Don’t delete the README however, as you’ll need it for later assignments.

This site is open source. Improve this page.