Development Wiki

Working with Git

From phpBB Development Wiki

Revision as of 15:37, 6 March 2010 by Naderman (Talk | contribs)

This gives some documentation on using git for phpBB development, details of the phpBB git infrastructure documents the repositories and branches available for use.

Command Line



Clone the main phpBB3 repository.

git clone git://


See phpBB3 Branches


Developers should fork a copy of the repository on GitHub from [1] and then clone as instructed by GitHub.


  • E-mail address:
    git config --add
  • Add the upstream remote (you can change 'upstream' to whatever you like):
    git remote add upstream git://

Creating local branches

To work on phpBB you need to create local branches of whichever develop branches you need, issue the following command to perform this operation:

git checkout -b develop origin/develop


Pulling in upstream changes

You will need to merge in changes made to the upstream repository for them to appear in your fork, the steps to do this follow. I'm assuming you are performing this on the develop branch, but it could be a bug fix branch or a develop release branch, so ensure you are on the correct branch using git branch and change with git checkout if required.

  1. Pull the changes from the upstream develop branch:
    git pull upstream develop
  2. Push the changes back to your fork (substitute develop for the current branch):
    git push origin develop

The following image visualises the phpBB 3 branching model. It may help to understand the different branches this section refers to later.

Error creating thumbnail: Unable to save thumbnail to destination

View in large or as svg.

Bug fixing

Ensure you are using the correct develop branch first and not a master branch. In this example we are using develop-olympus.

  1. git checkout develop-olympus # Checkout the base branch
  2. git branch bug/12345 # Create a new branch for your bug fix
  3. git checkout bug/12345 # Switch to the new branch
  4. Make your changes
  5. git add <files> # Stage the files
  6. git commit # Commit staged files - please use a correct commit message: Git Commit Messages
  7. git push origin bug/12345 # Push the branch back to github


Quick info for those with TortoiseGit (and used to working with TortoiseSVN)

Create your own SSH key

TortoiseGit will automatically use the SSH key

Note: I used the OpenSSH option during installation, so I am not sure if this works for the other option or if you are supposed to do it some other way


Then simply clone the repository to your local system and the rest is mostly like TortoiseSVN.


Grab the updates from upstream
Commits the changes locally (you must Push or Sync to commit the changes to the repository)
Pushes the changes that were locally made into the repository
Pushes/Pulls changes with more options

Further reading

External links