From: "Sean Kelley" <sean.v.kelley@gmail.com>
To: git@vger.kernel.org
Subject: Workflow example for remote repository use of GIT
Date: Tue, 28 Nov 2006 09:08:49 -0600 [thread overview]
Message-ID: <89b129c60611280708x10a9c42fia23e6b7770971838@mail.gmail.com> (raw)
I have been trying to set-up a workflow for developers in my group
using GIT. I came up with this simplified flow. Do you all see any
problems with this approach?
Thanks,
Sean
Always work out of master
git checkout master
Getting The Latest Upstream Code into master
git pull origin master
Create a topic branch for your development work
git checkout -b <new topic branch name>
Do your development in the topic branch
edit/debug/test
Committing Changes
git commit -a
Switch back to master
git checkout master
Update the master branch from origin again
git pull origin master
Now Merge your topic branch
git pull . <topic branch to merge into current branch>
How do I push my changes to the original repository?
git push origin master
--
next reply other threads:[~2006-11-28 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 15:08 Sean Kelley [this message]
2006-11-28 15:15 ` Workflow example for remote repository use of GIT Johannes Schindelin
2006-11-28 15:25 ` Shawn Pearce
2006-11-28 16:18 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89b129c60611280708x10a9c42fia23e6b7770971838@mail.gmail.com \
--to=sean.v.kelley@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).