Settings up git workflow

I am involved in project with three more developers and currently setting up the git repository in BitBucket. So far I have created the master repo and a develop branch. If I want to follow the git flow , how should I implement it? As in should I ask the other developers to checkout the developer branch and commit stuff straight to it or should they create their own branches based on the developer branch and create pull requests to when they need to commit something to developer branch ?

  • Bitbucket Permission denied (publickey) Git on OS X
  • Want to track a file / folder which was earlier ignored by .gitignore
  • reverse back to certain commit and test what the issue?
  • Can't create new branch.Unknown protocol
  • Remove .pyc files from Git remote repository
  • bitbucket stripped git revisions
  • If I Resolve a Conflict Does it Change Git Blame?
  • Put 10000 small text files to code base, will it make git slow?
  • Git Merge commits into an orphan branch
  • Git checkout from heroku
  • Git revert on published commits while maintaining ability to merge in future?
  • Git GUI.. stage everything
  • 2 Solutions collect form web for “Settings up git workflow”

    Regarding write access, either you install gitolite on your central repo server, or you manage two repositories:

    • one for the developer to push to
    • one for you to pull their work after review, trigger by merge request from the first one.

    A classic intermediate repo would be a gerrit one, which comes with its own review system.


    I would recommend starting with a simple workflow, based on GitHub-Flow at:
    A simple git branching model“, with the main elements being:

    1. master must always be deployable.
    2. all changes made through feature branches (pull-request + merge)
    3. rebase to avoid/resolve conflicts; merge in to master

    https://a248.e.akamai.net/camo.github.com/9783623eba280ba5ace8b9e63842be52af2f0546/687474703a2f2f7374617469632e62656e65742e61692f736b697463682f666c6f772d32303133303932362d3139333431392e706e67

    Then, when the release cycle becomes more complexe, you can have a look at git-flow.

    Where I work we have everybody use the git flow toolset. See https://github.com/nvie/gitflow/wiki/Installation for your OS. Anyway, once a developer have installed this and uses the commands provided there was much easier for us to get everybody on the same page. Especially since we use rebasing.

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