Skip to content

Commit dd9cbfd

Browse files
committed
More on README
1 parent 612e457 commit dd9cbfd

File tree

1 file changed

+38
-21
lines changed

1 file changed

+38
-21
lines changed

README.md

Lines changed: 38 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,7 @@ If you've used git for your own projects but haven't used it when collaborating
1010
If you're brand new to git, we'll be reviewing the basics at the beginning.
1111
If you're a git expert, feel free to share you expertise!
1212

13-
Topics we're hoping to cover:
14-
15-
* Branches
16-
* Merging & Rebasing (and why you might pick one over the other)
17-
* Git visualizers
18-
13+
This accompanies [slides](http://bit.do/git_tutorial).
1914
This tutorial was developed for [PyLadies Vancouver](http://www.pyladies.com/locations/vancouver/).
2015

2116

@@ -43,23 +38,32 @@ If you're unsure on any of those, see the [basics](docs/basics.md) section.
4338
Other prerequisites:
4439

4540
* A Github account
46-
* A computer with git installed
41+
* Git
42+
* Python
43+
* Command line (UNIX shell or Windows Powershell)
44+
45+
46+
## Goals
4747

48-
The tutorial covers:
48+
By the time you're done, you should know how to contribute to an open source project.
49+
We're covering how to:
4950

50-
* Concepts behind git
51-
* Git visualizers
52-
* Working with other people's code
53-
** Forking on Github and adding remotes
54-
** Branches
55-
** Merging
56-
** Rebasing
57-
* Recovering from problems
58-
** Merge conflicts
59-
** Aborting the current action
60-
** Committing to the wrong branch
61-
** Reset and reverting
62-
* Tips and Tricks
51+
* Fork a project
52+
* Make changes in a branch
53+
* Keep up with upstream changes
54+
* Make pull request
55+
* Merge a branch
56+
57+
We're also showing two workflows.
58+
59+
* Open-source contributor
60+
* Don't have commit access to the project repository
61+
* Must fork & make a pull request
62+
* Someone else merges changes
63+
* Core contributor / employee
64+
* Have commit access to the project repository
65+
* Can merge your own changes
66+
* Can still use pull requests to encourage code review
6367

6468

6569
## Other Resources
@@ -68,7 +72,20 @@ The tutorial covers:
6872
* [Pro Git](https://git-scm.com/book) - Comprehensive reference book for git
6973
* [The Git Parable](http://tom.preston-werner.com/2009/05/19/the-git-parable.html) - Story explaining the motivation behind git & version control
7074
* [Oh shit, git!](http://ohshitgit.com) - Amusing solutions to common problems
75+
* [Getting solid at Git rebase vs. merge](https://medium.com/@porteneuve/getting-solid-at-git-rebase-vs-merge-4fa1a48c53aa)
76+
77+
78+
## Created by
7179

80+
* Holly Becker
81+
* Python developer
82+
* Linux user
83+
* 4 years using git
84+
* @Hwesta on Twitter & Github
85+
* Ian Neufeld (Zee)
86+
* C# / Unity developer
87+
* Windows user
88+
* 8 years creating & resolving merge conflicts
7289

7390
## License
7491

0 commit comments

Comments
 (0)