Git hub party-20151008

GITHUBPARTY!
Thursday, 8 October, 2015
Savoir Faire Linux, Montreal
https://www.savoirfairelinux.com/

GITHUBPARTY
| Françoise Provencher  francoiseprovencher

INTRODUCTION
Link to .
Finding a project to collaborate in
the presentation
https://github.com/explore
https://github.com/showcases

GITHUBPARTY
| | Blanca Mancilla  bluciam  @Blanckus

PARTS
0.
1.
2.
3.
4.
5.
Introduction
Bare Basics
Sharing
Collaborating
Your turn
What is next?

Do you have your account already?
PART0
https://github.com/

Git is a free and open source distributed version control
system designed to handle everything from small to very
large projects with speed and efficiency.
GIT
https://git-scm.com/

Git is a widely used version control system for software
development. It is a distributed revision control system
with an emphasis on speed, data integrity, and support
for distributed, non-linear workflows.
GIT
https://en.wikipedia.org/wiki/Git

GIT
More technical definition and to really understand Git:
Setting up Git:
https://git-scm.com/book/en/v2/Getting-Started-Git-Basics
https://help.github.com/articles/set-up-git/

GITHUB
GitHub is a Web-based Git repository hosting service. It
offers a lot of the functionality of Git as well as adding its
own features.
https://en.wikipedia.org/wiki/GitHub

PARTI
Repositories
Forks
Issues
Branches
Local changes
Commits

A repository is the basic unit of GitHub, most commonly
a single project. Repositories can contain folders and
files, including images – anything your project needs.
REPOSITORIES

REPOSITORIES
https://github.com/bluciam/helloworld_pyladiesMTL

PARTI
Forks
Issues
Branches
Local changes
Commits
Repositories

A fork is a copy of a repository. Forking a repository
allows you to freely experiment with changes without
affecting the original project.
FORKS
Most commonly, forks are used to either propose
changes to someone else's project or to use someone
else's project as a starting point for your own idea.

FORKS
LET'SCREATEAFORK
1. Login into your GitHub account.
2. Head over to
3. Find the Fork tab and click on it.

Full instructions with commands for local repository:
FORKS
https://help.github.com/articles/fork-a-repo/

FORKS
Synchronizing your fork with the master repository.
There are two ways:
Making a pull-request into your own repository.
Using the command line.

PARTI
Issues
Branches
Local changes
Commits
Repositories
Forks

ISSUES
An Issue is a note on a repository about something that
needs attention. It could be a bug, a feature request, a
question or lots of other things.

PyLadies Montreal needs a logo!
ISSUES
LET'SCREATEANISSUE

ISSUES
YOURTURN!
Click on the issues link, to the right.
Click on New Issue.
Go Wild! Create! Comment!

PARTI
Branches
Local changes
Commits
Repositories
Forks
Issues

Branching is the way to work on different parts of a
repository at one time.
BRANCHES

BRANCHES
LET'SCREATEABRANCH
1. Head over to
2. Find the Branch: master tab and click on it.
3. Enter the name of the new branch: translate-README.
https://github.com/<your-github-handle>
/helloworld_pyladiesMTL

Full instructions at
BRANCHES
https://help.github.com/articles/creating-and-deleting-
branches-within-your-repository/

PARTI
Local changes
Commits
Repositories
Issues
Forks
Branches

MAKEACHANGE
CHANGEISGOOD!
CHANGEBRINGSHAPPINESS!
1. Head over to
2. Click on the issues link.
3. Choose an issue.

MAKEACHANGE
LET'SDOIT!
1. Head over to your own account.
2. Choose the branch you want to make the change in.
3. You can either add a file or modify an existing one.
4. Go wild!

Changes to a file can be done by clicking on the pencil
icon in the upper right corner.
Add a file by clicking on the plus sign after the directory
name.
MAKEACHANGE
LET'SDOIT!

MAKEACHANGE
Make a change in the master branch.
And in another branch.
In the same line.
Commit the changes separately.

PARTI
Commits
Repositories
Issues
Forks
Branches
Local changes

Commits are the heart of git and GitHub. They are the
saved changes on the repository.
COMMITYOURCHANGES
Each commit should have a message:
1. Think that you are writing an email to a future
contributor who will read this five years from now.
2. Explain why the change.
3. Remeber that git can already answer who, when and
what, so no need to add these.

COMMITYOURCHANGES
Make your changes.
Add a one-liner summarizing the change.
Add a summary of the change.
Click on the Commit changesbutton.
That's it!
Commit messages form a story of the project.

PARTI
Repositories
Issues
Forks
Branches
Local changes
Commits

PART2
Sharing changes!
Pull request
Comparing differences
Blame
Synching your fork

Pull Requests are the heart of collaboration on GitHub.
When you make a pull request, you’re proposing your
changes and requesting that someone pull in your
contribution - aka merge them into their branch.
PULLREQUEST

As soon as you make a change, you can open a Pull
Request. People use Pull Requests to start a discussion
about commits (code review) even before the code is
finished. This way you can get feedback as you go or help
when you’re stuck.
PULLREQUEST

PULLREQUEST
LET'SCREATEAPULLREQUEST
1.
2. Find the link to Pull Request on the right.
3. Click on it.
4. Click on the New pull request button.
5. Click on Create pull request.
You are presented with a screen to enter a message and
to choose which branch to ask the request on, if there
are many choices.

Instructions at
PULLREQUEST
https://help.github.com/articles/creating-a-pull-request/

The best is to see it in action...
PULLREQUEST
LET'SSEEIT!

PART2
Blame
Synching your fork
Pull request

It is another way to get to a Pull Request.
COMPARINGCHANGES

COMPARINGCHANGES
1. Head over to your own account.
2. Find the green button at the top next to the Branch
button. That will show you directly the differences
between the main repository and your local changes.

Again, the best is to see it in action...
COMPARINGCHANGES
LET'SSEEIT!

Click on the number next to the fork button to see the
network graph.
COMPARINGCHANGES

PART2
Blame
Synching your fork
Pull request

BLAME
The blamecommand is a Git feature, designed to help
you determine who made changes to a file.
Despite its negative-sounding name, git blameis
actually pretty innocuous; its primary function is to point
out who changed which lines in a file, and why. It can be
a useful tool to identify changes in your code.

Instructions at
BLAME
https://help.github.com/articles/using-git-blame-to-trace-
changes-in-a-file/

PART2
Synching your fork
Pull request
Blame

SYNCHINGYOURFORK
Click on the compare button.
Click on Compare across forks.
Choose the branches that are difference.

PART2
Pull request
Blame
Synching your fork

PART3
Collaboration!
Create a repository
Add collaborators
Be Social

CREATEAREPOSITORY
We are going to create a super heroine project!
We will call it super-heroines-pyladiesMTL.
Let's do it!

PART3
Add collaborators
Be Social
Create a repository

ADDCOLLABORATORS
https://help.github.com/articles/adding-collaborators-to-
a-personal-repository/

PART3
Be Social
Create a repository
Add collaborators

BESOCIAL
https://help.github.com/articles/be-social/

PART3
Create a repository
Add collaborators
Be Social

PART4
Your turn!
Create your own repository
Ideas:
Python tutorial exercises
Your thesis
Talks
Your CV
Your coding project

WHATISNEXT?
Interaction between the git command line and github,
that is, your local repository and repo in the cloud.

GITHUBPARTY
| Françoise Provencher  francoiseprovencher
| | Blanca Mancilla  bluciam  @Blanckus

Git hub party-20151008

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (20)

Similar a Git hub party-20151008

Similar a Git hub party-20151008 (20)

Último

Último (20)

Git hub party-20151008