Is this a suggested process for using GitHub with a team?

I am getting help from other developers for the first time on a repo that I am administrating, and I want to make sure I understand how the flow of work should go. The repo is setup under an Organization, and the other developers are members of a team with read access. I have owner access. Here is what I am thinking would be the flow of work:

  1. He forks the repo
  2. He creates a new branch
  3. He makes changes, adding commits
  4. He submits a pull request
  5. I merge the pull request into the upstream branch

Am I on the right track here?

  • List all commits in a topic branch
  • Azure websites deploy specific web project
  • Ignore all files with the same name in git
  • How to tell Git to always pull the master branch?
  • On git push I got error: error: invalid protocol: wanted 'old new ref'
  • Git Remote: Show a Custom Message, at Every Clone/Fetch?
  • Is there a way to modify the width of elements in the IntelliJ statusbar (esp, the current git branch)
  • Git command for count of commit messages containing a string, per user
  • Time of commit pushed to remote
  • set up git alias, but then calling it gives 'command not found'
  • list all files having a git attribute set
  • Git: how to overcome file structure restrictions?
  • One Solution collect form web for “Is this a suggested process for using GitHub with a team?”

    Yes, that’s how we do things. (He makes the branch on his own fork.) But what you’re missing is how people keep their own branches coordinated with the main fork’s master branch.

    We handle this by regularly rebasing off the main “upstream” branch’s master, and using our own repository’s master branch as a copy of upstream’s:

    On our own repository’s master:

    $ git fetch upstream
    $ git rebase upstream/master
    $ git push origin master

    Periodically, on our branches:

    $ git rebase master

    We’re also careful to avoid changing the same lines of the same files.

    Git Baby is a git and github fan, let's start git clone.