Git workflow

The suggested workflow when working in a somewhat large project with git, given that one does not use Gerrit or a similar tool, is a rather general pull request based flow. The following flow is general enough so that it works in both GitHub, GitLab and Bitbucket, at least.

Assume in the examples below that the URL to the repo is

General setup

  1. Fork the repo. In most git frontends, that fork will end up at<username>/software-factory.git

  2. Clone the original fork and add a remote for the upstream to the repo

    $ git clone<username>/software-factory.git
    $ git remote add upstream

This will make the fork have origin as remote name, which we think feels most natural for most developers, as it is the repository the developer will typically push to. On the other hand, we recommend to always type the remote and branch name when pushing, which forces the developer to be more explicit about their intentions.

If you didn’t manage to clone the repo via the steps above, it most likely due to the SSH key hasn’t been set up yet. To quick fix

$ ssh-keygen -t rsa -b 4096 -C ""
# This will generate a new ssh key for you

$ sudo apt-get install xclip
# Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)

$ xclip -sel clip < ~/.ssh/
# Copies the contents of the file to your clipboard

Then add your new SSH key to the account on the git web frontend. A long guide (for GitHub) can be found here:

For each set of changes

  1. Check out the master branch and make sure it is up to date

    $ git checkout master
    $ git pull upstream master
    $ git push origin master
  2. Check out a new branch to work on

    $ git checkout -b some_branch_name

    This is optional, it is possible to work on master as well, but it has the downside of making master blocked while waiting for merge.

  3. Do some work, and commit it.

    $ touch new_file
    $ git add new_file
    $ git commit -s -m "add new_file"
  4. Make sure your branch is up-to-date with master

    $ git pull upstream master --rebase

    This is to make sure that any conflicts that exist before pushing are resolved locally before pushing. It might be the case that there are more people working on the same code that has a pull request which just got accepted, which would lead to a conflict in master. Then it is better to resolve the conflict in the local branch before creating a new pull request. To keep the git log clear of empty merge commits, we recommend rebasing.

  5. Push to the forked remote

    $ git push origin some_branch_name
  6. Create a pull request in whatever web frontend for git is being used

  7. Clean up after the pull request get merged (optional)

    $ git checkout master
    $ git branch -D some_branch_name
    $ git push origin :some_branch_name

Make sure the rest of the team is notified of the pull request. There are different ways of handling changes to the pull request. Either any new changes can be added to an existing commit and force-pushed to the forked repo, or they can be added on top of the existing commit. The pull request will be updated either way.

Whenever the team is satisfied with the changes, pull the changes in by accepting the pull request.

Good commits

A good commit (or patch):

  1. is atomic: Each commit should contain only one logical change. Use of vague verbs (e.g “update”) and phrases like “this patch also” are usually a good indicator that commit is not atomic.
  2. has a good commit message associated with it.

Good commit messages are important because of two reasons:

  1. Proper history: Each line in the source code can then be traced to the commit that changed it and why. Humans tend to have bad memory so even the committer may not remember why they made some particular changes after a few months or years of the commit.
  2. Ease of reviewing: The reviewer need to know why you are suggesting the changes in question when you submit a pull-request and they can not always infer the rationale from the changes themselves.

Keeping in mind that the topic of what qualifies as a good commit message, is highly subjective, the authors of this document follow and highly recommend GNOME’s commit message guidelines.