1.
Ready! Workflows

2.
Question time
at the end
Submit your
questions

3.
Nicola Paolucci
Developer Advocate / Git Evangelist
@durdndurdn.comI come out nice in pictures, I know :-).

4.
Cheap local branching
Full local history
Speed
Staging area
prominent in Open Source
Huge community
You heard has
Feature based workflow
10x the speed of svn
Distributed
cryptographic integrity

5.
ground breaking paradigm
is ground breaking

6.
Workflow building blocks

7.
1
Common Practices
2
3
Collaboration model
We’ll cover how to choose:
Branching model
Continuous Integration4

8.
Which collaboration model?1
Easy, right?

9.
Fully decentralized
Anarchy
I do my thing
I do my thing, too
ANARCHY
here’s mine, who tells
john?
look ma, a goat!

10.
Blessed repository with
Gatekeeper
He is cool
Gatekeeper
To have your work
accepted, talk to him

11.
and Lieutenants
Dictator
long live the King!
Lieutenants guard
the King
Blessed repository

12.
Shared common
repository
we share “everything”
luckily no goats here
Centralised

13.
atlassian.com/git
More on Collaboration models

14.
+ = Centralized
Enterprise

15.
Centralized allows fine
grained ACLs
Branch & Repo permissions

16.
Integration with your
Issue tracking and CI

17.
Which branching model?2

18.
Product Releases1
Continuous Delivery2
Two common Branching Models

19.
for Product Releases2.1

20.
One Central Repository1
One Branch per Feature
One Branch per Bugfix
2
3
Time
master
feature
branches
PRJ-123-description

21.
One Central Repository1
One Branch per Feature
One Branch per Bugfix
2
3
Time
master
bugfix
branch
PRJ-123-bug-description

22.
Stable Branches4
master is alpha / RC5
Pull Requests6
Before merges
Long running
Time
master
stable
branch
PRJ-345-bug-description
bugfix
2.2

23.
2.2 for Continuous Delivery

24.
master is in production1
staging is the next version
new features off staging
2
3
with branch names like: username/ISSUE-KEY-summary
promoted from staging, can receive hot-fixes

25.
Common Practices3
turbo boost!

26.
What is a Pull Request?

27.
Hey I have some code I
want to merge here,
take a look?
Low friction
collaboration
Pull Request
I have some
code here!
Can I merge
it here?

28.
Single Repository
vs
Remote Forks

29.
Complete visibility1
No per Dev remotes required
KISS
2
3
Pros of a Single Repo
All feature
branches
available

30.
Forks
Are Great too BTW

31.
Every one has their
remote repository
With Forks
Full remote copy,
each has one
Integrator, Gatekeeper,
Tech Lead, etc.

32.
Manage codebase maturity1
X department and 3rd parties
Dev to Dev interactions
2
3
Read “Cross”

33.
Continuous Integration4

34.
What happens to CI with git?1
An explosion of branches2
3 Performance degradation of build sys

35.
Building everything is expensive1
Automatically build stable and master2
3 Manually trigger feature branch builds

36.
Less Friction and Automation5

37.
Code Quality
via pre-commit hooks

38.
Branch from green builds

39.
Automatic merges for the win!

40.
Time
master
stable
branch
PRJ-345-bug-description
bugfix
2.2
stable
branch
2.1
Automatic MERGES!

41.
Ripple merges1
Server side update hook2
3 Or tool support

42.
Read more at:
bitly.com/automatic-merges

43.
In Conclusion: the recipe

44.
Branching
Model
Adopt Git
Practices
Automation &
CI setup
Conclusions
Product
workflow
Continuous
delivery
workflow
Embrace PR
Build
automatically,
but leave
knobs!
Single Repo
or Forks
Collaboration
Model
Centralized
Hooks, hooks
everywhere

45.
Nicola Paolucci
THANKS YOU FOR YOUR ATTENTION
@durdndurdn.comShould I change the pic?

46.
Git Repository Management
for Enterprise Teams
Free Git Code Hosting
for Small Teams
Free Git Desktop client
for Mac or Windows
Atlassian