<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect2 SYSTEM "../../../dtd/dblite.dtd">

<sect2 lang="en" id="giteveryday(7)">
    <title>giteveryday(7)</title>
    <date>2024-07-02</date>
<revhistory><revision><date>2024-07-02</date></revision></revhistory>
<indexterm>
<primary>giteveryday(7)</primary>
</indexterm>
<simplesect id="giteveryday(7)__name">
<title>NAME</title>
<simpara>giteveryday - A useful minimum set of commands for Everyday Git</simpara>
</simplesect>
<simplesect id="giteveryday(7)__synopsis">
<title>SYNOPSIS</title>
<simpara>Everyday Git With 20 Commands Or So</simpara>
</simplesect>
<simplesect id="giteveryday(7)__description">
<title>DESCRIPTION</title>
<simpara>Git users can broadly be grouped into four categories for the purposes of
describing here a small set of useful commands for everyday Git.</simpara>
<itemizedlist>
<listitem>
<simpara>
<link linkend="giteveryday(7)_STANDALONE">Individual Developer (Standalone)</link> commands are essential
        for anybody who makes a commit, even for somebody who works alone.
</simpara>
</listitem>
<listitem>
<simpara>
If you work with other people, you will need commands listed in
        the <link linkend="giteveryday(7)_PARTICIPANT">Individual Developer (Participant)</link> section as well.
</simpara>
</listitem>
<listitem>
<simpara>
People who play the <link linkend="giteveryday(7)_INTEGRATOR">Integrator</link> role need to learn some
        more commands in addition to the above.
</simpara>
</listitem>
<listitem>
<simpara>
<link linkend="giteveryday(7)_ADMINISTRATION">Repository Administration</link> commands are for system
        administrators who are responsible for the care and feeding
        of Git repositories.
</simpara>
</listitem>
</itemizedlist>
</simplesect>
<simplesect id="giteveryday(7)__individual_developer_standalone_anchor_id_giteveryday_7__standalone_xreflabel_standalone">
<title>Individual Developer (Standalone)<anchor id="giteveryday(7)_STANDALONE" xreflabel="[STANDALONE]"/></title>
<simpara>A standalone individual developer does not exchange patches with
other people, and works alone in a single repository, using the
following commands.</simpara>
<itemizedlist>
<listitem>
<simpara>
<xref linkend="git-init(1)" /> to create a new repository.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-log(1)" /> to see what happened.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-switch(1)" /> and <xref linkend="git-branch(1)" /> to switch
    branches.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-add(1)" /> to manage the index file.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-diff(1)" /> and <xref linkend="git-status(1)" /> to see what
    you are in the middle of doing.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-commit(1)" /> to advance the current branch.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-restore(1)" /> to undo changes.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-merge(1)" /> to merge between local branches.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-rebase(1)" /> to maintain topic branches.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-tag(1)" /> to mark a known point.
</simpara>
</listitem>
</itemizedlist>
<section id="giteveryday(7)__examples">
<title>Examples</title>
<variablelist>
<varlistentry>
<term>
Use a tarball as a starting point for a new repository.
</term>
<listitem>
<screen>$ tar zxf frotz.tar.gz
$ cd frotz
$ git init
$ git add . <co id="giteveryday_CO1-1"/>
$ git commit -m "import of frotz source tree."
$ git tag v2.43 <co id="giteveryday_CO1-2"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO1-1">
<para>
add everything under the current directory.
</para>
</callout>
<callout arearefs="giteveryday_CO1-2">
<para>
make a lightweight, unannotated tag.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
<varlistentry>
<term>
Create a topic branch and develop.
</term>
<listitem>
<screen>$ git switch -c alsa-audio <co id="giteveryday_CO2-1"/>
$ edit/compile/test
$ git restore curses/ux_audio_oss.c <co id="giteveryday_CO2-2"/>
$ git add curses/ux_audio_alsa.c <co id="giteveryday_CO2-3"/>
$ edit/compile/test
$ git diff HEAD <co id="giteveryday_CO2-4"/>
$ git commit -a -s <co id="giteveryday_CO2-5"/>
$ edit/compile/test
$ git diff HEAD^ <co id="giteveryday_CO2-6"/>
$ git commit -a --amend <co id="giteveryday_CO2-7"/>
$ git switch master <co id="giteveryday_CO2-8"/>
$ git merge alsa-audio <co id="giteveryday_CO2-9"/>
$ git log --since='3 days ago' <co id="giteveryday_CO2-10"/>
$ git log v2.43.. curses/ <co id="giteveryday_CO2-11"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO2-1">
<para>
create a new topic branch.
</para>
</callout>
<callout arearefs="giteveryday_CO2-2">
<para>
revert your botched changes in <emphasis>curses/ux_audio_oss.c</emphasis>.
</para>
</callout>
<callout arearefs="giteveryday_CO2-3">
<para>
you need to tell Git if you added a new file; removal and
modification will be caught if you do <emphasis>git commit -a</emphasis> later.
</para>
</callout>
<callout arearefs="giteveryday_CO2-4">
<para>
to see what changes you are committing.
</para>
</callout>
<callout arearefs="giteveryday_CO2-5">
<para>
commit everything, as you have tested, with your sign-off.
</para>
</callout>
<callout arearefs="giteveryday_CO2-6">
<para>
look at all your changes including the previous commit.
</para>
</callout>
<callout arearefs="giteveryday_CO2-7">
<para>
amend the previous commit, adding all your new changes,
using your original message.
</para>
</callout>
<callout arearefs="giteveryday_CO2-8">
<para>
switch to the master branch.
</para>
</callout>
<callout arearefs="giteveryday_CO2-9">
<para>
merge a topic branch into your master branch.
</para>
</callout>
<callout arearefs="giteveryday_CO2-10">
<para>
review commit logs; other forms to limit output can be
combined and include <emphasis>-10</emphasis> (to show up to 10 commits),
<emphasis>--until=2005-12-10</emphasis>, etc.
</para>
</callout>
<callout arearefs="giteveryday_CO2-11">
<para>
view only the changes that touch what's in <emphasis>curses/</emphasis>
directory, since <emphasis>v2.43</emphasis> tag.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
</variablelist>
</section>
</simplesect>
<simplesect id="giteveryday(7)__individual_developer_participant_anchor_id_giteveryday_7__participant_xreflabel_participant">
<title>Individual Developer (Participant)<anchor id="giteveryday(7)_PARTICIPANT" xreflabel="[PARTICIPANT]"/></title>
<simpara>A developer working as a participant in a group project needs to
learn how to communicate with others, and uses these commands in
addition to the ones needed by a standalone developer.</simpara>
<itemizedlist>
<listitem>
<simpara>
<xref linkend="git-clone(1)" /> from the upstream to prime your local
    repository.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-pull(1)" /> and <xref linkend="git-fetch(1)" /> from "origin"
    to keep up-to-date with the upstream.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-push(1)" /> to shared repository, if you adopt CVS
    style shared repository workflow.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-format-patch(1)" /> to prepare e-mail submission, if
    you adopt Linux kernel-style public forum workflow.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-send-email(1)" /> to send your e-mail submission without
    corruption by your MUA.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-request-pull(1)" /> to create a summary of changes
    for your upstream to pull.
</simpara>
</listitem>
</itemizedlist>
<section id="giteveryday(7)__examples_2">
<title>Examples</title>
<variablelist>
<varlistentry>
<term>
Clone the upstream and work on it.  Feed changes to upstream.
</term>
<listitem>
<screen>$ git clone git://git.kernel.org/pub/scm/.../torvalds/linux-2.6 my2.6
$ cd my2.6
$ git switch -c mine master <co id="giteveryday_CO3-1"/>
$ edit/compile/test; git commit -a -s <co id="giteveryday_CO3-2"/>
$ git format-patch master <co id="giteveryday_CO3-3"/>
$ git send-email --to="person &lt;email@example.com&gt;" 00*.patch <co id="giteveryday_CO3-4"/>
$ git switch master <co id="giteveryday_CO3-5"/>
$ git pull <co id="giteveryday_CO3-6"/>
$ git log -p ORIG_HEAD.. arch/i386 include/asm-i386 <co id="giteveryday_CO3-7"/>
$ git ls-remote --heads http://git.kernel.org/.../jgarzik/libata-dev.git <co id="giteveryday_CO3-8"/>
$ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL <co id="giteveryday_CO3-9"/>
$ git reset --hard ORIG_HEAD <co id="giteveryday_CO3-10"/>
$ git gc <co id="giteveryday_CO3-11"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO3-1">
<para>
checkout a new branch <emphasis>mine</emphasis> from master.
</para>
</callout>
<callout arearefs="giteveryday_CO3-2">
<para>
repeat as needed.
</para>
</callout>
<callout arearefs="giteveryday_CO3-3">
<para>
extract patches from your branch, relative to master,
</para>
</callout>
<callout arearefs="giteveryday_CO3-4">
<para>
and email them.
</para>
</callout>
<callout arearefs="giteveryday_CO3-5">
<para>
return to <emphasis>master</emphasis>, ready to see what's new
</para>
</callout>
<callout arearefs="giteveryday_CO3-6">
<para>
<emphasis>git pull</emphasis> fetches from <emphasis>origin</emphasis> by default and merges into the
current branch.
</para>
</callout>
<callout arearefs="giteveryday_CO3-7">
<para>
immediately after pulling, look at the changes done upstream
since last time we checked, only in the
area we are interested in.
</para>
</callout>
<callout arearefs="giteveryday_CO3-8">
<para>
check the branch names in an external repository (if not known).
</para>
</callout>
<callout arearefs="giteveryday_CO3-9">
<para>
fetch from a specific branch <emphasis>ALL</emphasis> from a specific repository
and merge it.
</para>
</callout>
<callout arearefs="giteveryday_CO3-10">
<para>
revert the pull.
</para>
</callout>
<callout arearefs="giteveryday_CO3-11">
<para>
garbage collect leftover objects from reverted pull.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
<varlistentry>
<term>
Push into another repository.
</term>
<listitem>
<screen>satellite$ git clone mothership:frotz frotz <co id="giteveryday_CO4-1"/>
satellite$ cd frotz
satellite$ git config --get-regexp '^(remote|branch)\.' <co id="giteveryday_CO4-2"/>
remote.origin.url mothership:frotz
remote.origin.fetch refs/heads/*:refs/remotes/origin/*
branch.master.remote origin
branch.master.merge refs/heads/master
satellite$ git config remote.origin.push \
           +refs/heads/*:refs/remotes/satellite/* <co id="giteveryday_CO4-3"/>
satellite$ edit/compile/test/commit
satellite$ git push origin <co id="giteveryday_CO4-4"/>

mothership$ cd frotz
mothership$ git switch master
mothership$ git merge satellite/master <co id="giteveryday_CO4-5"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO4-1">
<para>
mothership machine has a frotz repository under your home
directory; clone from it to start a repository on the satellite
machine.
</para>
</callout>
<callout arearefs="giteveryday_CO4-2">
<para>
clone sets these configuration variables by default.
It arranges <emphasis>git pull</emphasis> to fetch and store the branches of mothership
machine to local <emphasis>remotes/origin/*</emphasis> remote-tracking branches.
</para>
</callout>
<callout arearefs="giteveryday_CO4-3">
<para>
arrange <emphasis>git push</emphasis> to push all local branches to
their corresponding branch of the mothership machine.
</para>
</callout>
<callout arearefs="giteveryday_CO4-4">
<para>
push will stash all our work away on <emphasis>remotes/satellite/*</emphasis>
remote-tracking branches on the mothership machine.  You could use this
as a back-up method. Likewise, you can pretend that mothership
"fetched" from you (useful when access is one sided).
</para>
</callout>
<callout arearefs="giteveryday_CO4-5">
<para>
on mothership machine, merge the work done on the satellite
machine into the master branch.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
<varlistentry>
<term>
Branch off of a specific tag.
</term>
<listitem>
<screen>$ git switch -c private2.6.14 v2.6.14 <co id="giteveryday_CO5-1"/>
$ edit/compile/test; git commit -a
$ git checkout master
$ git cherry-pick v2.6.14..private2.6.14 <co id="giteveryday_CO5-2"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO5-1">
<para>
create a private branch based on a well known (but somewhat behind)
tag.
</para>
</callout>
<callout arearefs="giteveryday_CO5-2">
<para>
forward port all changes in <emphasis>private2.6.14</emphasis> branch to <emphasis>master</emphasis> branch
without a formal "merging". Or longhand<?asciidoc-br?>
<emphasis>git format-patch -k -m --stdout v2.6.14..private2.6.14 |
  git am -3 -k</emphasis>
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
</variablelist>
<simpara>An alternate participant submission mechanism is using the
<emphasis>git request-pull</emphasis> or pull-request mechanisms (e.g. as used on
GitHub (www.github.com) to notify your upstream of your
contribution.</simpara>
</section>
</simplesect>
<simplesect id="giteveryday(7)__integrator_anchor_id_giteveryday_7__integrator_xreflabel_integrator">
<title>Integrator<anchor id="giteveryday(7)_INTEGRATOR" xreflabel="[INTEGRATOR]"/></title>
<simpara>A fairly central person acting as the integrator in a group
project receives changes made by others, reviews and integrates
them and publishes the result for others to use, using these
commands in addition to the ones needed by participants.</simpara>
<simpara>This section can also be used by those who respond to <emphasis>git
request-pull</emphasis> or pull-request on GitHub (www.github.com) to
integrate the work of others into their history. A sub-area
lieutenant for a repository will act both as a participant and
as an integrator.</simpara>
<itemizedlist>
<listitem>
<simpara>
<xref linkend="git-am(1)" /> to apply patches e-mailed in from your
    contributors.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-pull(1)" /> to merge from your trusted lieutenants.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-format-patch(1)" /> to prepare and send suggested
    alternative to contributors.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-revert(1)" /> to undo botched commits.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-push(1)" /> to publish the bleeding edge.
</simpara>
</listitem>
</itemizedlist>
<section id="giteveryday(7)__examples_3">
<title>Examples</title>
<variablelist>
<varlistentry>
<term>
A typical integrator's Git day.
</term>
<listitem>
<screen>$ git status <co id="giteveryday_CO6-1"/>
$ git branch --no-merged master <co id="giteveryday_CO6-2"/>
$ mailx <co id="giteveryday_CO6-3"/>
&amp; s 2 3 4 5 ./+to-apply
&amp; s 7 8 ./+hold-linus
&amp; q
$ git switch -c topic/one master
$ git am -3 -i -s ./+to-apply <co id="giteveryday_CO6-4"/>
$ compile/test
$ git switch -c hold/linus &amp;&amp; git am -3 -i -s ./+hold-linus <co id="giteveryday_CO6-5"/>
$ git switch topic/one &amp;&amp; git rebase master <co id="giteveryday_CO6-6"/>
$ git switch -C seen next <co id="giteveryday_CO6-7"/>
$ git merge topic/one topic/two &amp;&amp; git merge hold/linus <co id="giteveryday_CO6-8"/>
$ git switch maint
$ git cherry-pick master~4 <co id="giteveryday_CO6-9"/>
$ compile/test
$ git tag -s -m "GIT 0.99.9x" v0.99.9x <co id="giteveryday_CO6-10"/>
$ git fetch ko &amp;&amp; for branch in master maint next seen <co id="giteveryday_CO6-11"/>
    do
        git show-branch ko/$branch $branch <co id="giteveryday_CO6-12"/>
    done
$ git push --follow-tags ko <co id="giteveryday_CO6-13"/></screen>
<calloutlist>
<callout arearefs="giteveryday_CO6-1">
<para>
see what you were in the middle of doing, if anything.
</para>
</callout>
<callout arearefs="giteveryday_CO6-2">
<para>
see which branches haven't been merged into <emphasis>master</emphasis> yet.
Likewise for any other integration branches e.g. <emphasis>maint</emphasis>, <emphasis>next</emphasis>
and <emphasis>seen</emphasis>.
</para>
</callout>
<callout arearefs="giteveryday_CO6-3">
<para>
read mails, save ones that are applicable, and save others
that are not quite ready (other mail readers are available).
</para>
</callout>
<callout arearefs="giteveryday_CO6-4">
<para>
apply them, interactively, with your sign-offs.
</para>
</callout>
<callout arearefs="giteveryday_CO6-5">
<para>
create topic branch as needed and apply, again with sign-offs.
</para>
</callout>
<callout arearefs="giteveryday_CO6-6">
<para>
rebase internal topic branch that has not been merged to the
master or exposed as a part of a stable branch.
</para>
</callout>
<callout arearefs="giteveryday_CO6-7">
<para>
restart <emphasis>seen</emphasis> every time from the next.
</para>
</callout>
<callout arearefs="giteveryday_CO6-8">
<para>
and bundle topic branches still cooking.
</para>
</callout>
<callout arearefs="giteveryday_CO6-9">
<para>
backport a critical fix.
</para>
</callout>
<callout arearefs="giteveryday_CO6-10">
<para>
create a signed tag.
</para>
</callout>
<callout arearefs="giteveryday_CO6-11">
<para>
make sure master was not accidentally rewound beyond that
already pushed out.
</para>
</callout>
<callout arearefs="giteveryday_CO6-12">
<para>
In the output from <emphasis>git show-branch</emphasis>, <emphasis>master</emphasis> should have
everything <emphasis>ko/master</emphasis> has, and <emphasis>next</emphasis> should have
everything <emphasis>ko/next</emphasis> has, etc.
</para>
</callout>
<callout arearefs="giteveryday_CO6-13">
<para>
push out the bleeding edge, together with new tags that point
into the pushed history.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
</variablelist>
<simpara>In this example, the <emphasis>ko</emphasis> shorthand points at the Git maintainer's
repository at kernel.org, and looks like this:</simpara>
<screen>(in .git/config)
[remote "ko"]
        url = kernel.org:/pub/scm/git/git.git
        fetch = refs/heads/*:refs/remotes/ko/*
        push = refs/heads/master
        push = refs/heads/next
        push = +refs/heads/seen
        push = refs/heads/maint</screen>
</section>
</simplesect>
<simplesect id="giteveryday(7)__repository_administration_anchor_id_giteveryday_7__administration_xreflabel_administration">
<title>Repository Administration<anchor id="giteveryday(7)_ADMINISTRATION" xreflabel="[ADMINISTRATION]"/></title>
<simpara>A repository administrator uses the following tools to set up
and maintain access to the repository by developers.</simpara>
<itemizedlist>
<listitem>
<simpara>
<xref linkend="git-daemon(1)" /> to allow anonymous download from
    repository.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-shell(1)" /> can be used as a <emphasis>restricted login shell</emphasis>
    for shared central repository users.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="git-http-backend(1)" /> provides a server side implementation
    of Git-over-HTTP ("Smart http") allowing both fetch and push services.
</simpara>
</listitem>
<listitem>
<simpara>
<xref linkend="gitweb(1)" /> provides a web front-end to Git repositories,
    which can be set-up using the <xref linkend="git-instaweb(1)" /> script.
</simpara>
</listitem>
</itemizedlist>
<simpara><ulink url="https://www.kernel.org/pub/software/scm/git/docs/howto/update-hook-example.html"><citetitle>update hook howto</citetitle></ulink> has a good
example of managing a shared central repository.</simpara>
<simpara>In addition there are a number of other widely deployed hosting, browsing
and reviewing solutions such as:</simpara>
<itemizedlist>
<listitem>
<simpara>
gitolite, gerrit code review, cgit and others.
</simpara>
</listitem>
</itemizedlist>
<section id="giteveryday(7)__examples_4">
<title>Examples</title>
<variablelist>
<varlistentry>
<term>
We assume the following in /etc/services
</term>
<listitem>
<screen>$ grep 9418 /etc/services
git             9418/tcp                # Git Version Control System</screen>
</listitem>
</varlistentry>
<varlistentry>
<term>
Run git-daemon to serve /pub/scm from inetd.
</term>
<listitem>
<screen>$ grep git /etc/inetd.conf
git     stream  tcp     nowait  nobody \
  /usr/bin/git-daemon git-daemon --inetd --export-all /pub/scm</screen>
<simpara>The actual configuration line should be on one line.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
Run git-daemon to serve /pub/scm from xinetd.
</term>
<listitem>
<screen>$ cat /etc/xinetd.d/git-daemon
# default: off
# description: The Git server offers access to Git repositories
service git
{
        disable = no
        type            = UNLISTED
        port            = 9418
        socket_type     = stream
        wait            = no
        user            = nobody
        server          = /usr/bin/git-daemon
        server_args     = --inetd --export-all --base-path=/pub/scm
        log_on_failure  += USERID
}</screen>
<simpara>Check your xinetd(8) documentation and setup, this is from a Fedora system.
Others might be different.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
Give push/pull only access to developers using git-over-ssh.
</term>
<listitem>
<simpara>
e.g. those using:
<emphasis>$ git push/pull ssh://host.xz/pub/scm/project</emphasis>
</simpara>
<screen>$ grep git /etc/passwd <co id="giteveryday_CO7-1"/>
alice:x:1000:1000::/home/alice:/usr/bin/git-shell
bob:x:1001:1001::/home/bob:/usr/bin/git-shell
cindy:x:1002:1002::/home/cindy:/usr/bin/git-shell
david:x:1003:1003::/home/david:/usr/bin/git-shell
$ grep git /etc/shells <co id="giteveryday_CO7-2"/>
/usr/bin/git-shell</screen>
<calloutlist>
<callout arearefs="giteveryday_CO7-1">
<para>
log-in shell is set to /usr/bin/git-shell, which does not
allow anything but <emphasis>git push</emphasis> and <emphasis>git pull</emphasis>.  The users require
ssh access to the machine.
</para>
</callout>
<callout arearefs="giteveryday_CO7-2">
<para>
in many distributions /etc/shells needs to list what is used
as the login shell.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
<varlistentry>
<term>
CVS-style shared repository.
</term>
<listitem>
<screen>$ grep git /etc/group <co id="giteveryday_CO8-1"/>
git:x:9418:alice,bob,cindy,david
$ cd /home/devo.git
$ ls -l <co id="giteveryday_CO8-2"/>
  lrwxrwxrwx   1 david git    17 Dec  4 22:40 HEAD -&gt; refs/heads/master
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 branches
  -rw-rw-r--   1 david git    84 Dec  4 22:40 config
  -rw-rw-r--   1 david git    58 Dec  4 22:40 description
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 hooks
  -rw-rw-r--   1 david git 37504 Dec  4 22:40 index
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 info
  drwxrwsr-x   4 david git  4096 Dec  4 22:40 objects
  drwxrwsr-x   4 david git  4096 Nov  7 14:58 refs
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 remotes
$ ls -l hooks/update <co id="giteveryday_CO8-3"/>
  -r-xr-xr-x   1 david git  3536 Dec  4 22:40 update
$ cat info/allowed-users <co id="giteveryday_CO8-4"/>
refs/heads/master       alice\|cindy
refs/heads/doc-update   bob
refs/tags/v[0-9]*       david</screen>
<calloutlist>
<callout arearefs="giteveryday_CO8-1">
<para>
place the developers into the same git group.
</para>
</callout>
<callout arearefs="giteveryday_CO8-2">
<para>
and make the shared repository writable by the group.
</para>
</callout>
<callout arearefs="giteveryday_CO8-3">
<para>
use update-hook example by Carl from Documentation/howto/
for branch policy control.
</para>
</callout>
<callout arearefs="giteveryday_CO8-4">
<para>
alice and cindy can push into master, only bob can push into doc-update.
david is the release manager and is the only person who can
create and push version tags.
</para>
</callout>
</calloutlist>
</listitem>
</varlistentry>
</variablelist>
</section>
</simplesect>
<simplesect id="giteveryday(7)__git">
<title>GIT</title>
<simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
</simplesect>
</sect2>
