Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Git] Curriculum Split & Overhaul #485

Open
hyendler opened this issue Aug 1, 2017 · 2 comments
Open

[Git] Curriculum Split & Overhaul #485

hyendler opened this issue Aug 1, 2017 · 2 comments

Comments

@hyendler
Copy link
Contributor

hyendler commented Aug 1, 2017

This is a sizeable issue. The main goal that needs to be accomplished is splitting the Git curriculum into two different classes - 1) Git 2) Github

  1. Git
  • what is version control
  • installation
  • introduction to git (what is a repo, branch, commit)
  • creating repo, tracking files, committing
  • undoing changes (after making changes, after git adding, and after committing)
  • branching (what is a branch, how to create new branch, how to checkout)
  • merging (why do we need a master)
  • git workflow (on local - checkout a feature branch, create changes, commit, repeat, merge branch in)
  1. Github & Group git workflow
  • what is github
  • multiple ways to create repos (on local then sync with remote, or on remote then clone to local)
  • how to add contributors
  • what is a pull request
  • git workflow with pull request (create feature branch on local, push to origin, create pull request, merge into master, pull master down, delete feature branch)
  • what is forking?
  • git workflow with forking
  • git ignore if there is time (should not be in part one)
@hyendler
Copy link
Contributor Author

hyendler commented Aug 1, 2017

can't decide where merge conflicts should go - maybe both?

@hyendler
Copy link
Contributor Author

hyendler commented Aug 1, 2017

also in git, introduce slides involving a recap of command line - what is the terminal, how to move between files (cd), how to create a new file, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant