git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Workflow example for remote repository use of GIT

From
SKSean Kelley <sean.v.kelley@gmail.com>
Date
Nov 28, 2006, 15:08 UTC
Message-ID
<89b129c60611280708x10a9c42fia23e6b7770971838@mail.gmail.com>

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: Johannes Schindelin
Message 1 of 4 in “Workflow example for remote repository use of GIT”
  1. Sean KelleyNov 28, 2006
  2. Johannes SchindelinNov 28, 2006
  3. Shawn PearceNov 28, 2006
  4. Jakub NarebskiNov 28, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.