Jump to content

Community Involvement: PR Reviews


Recommended Posts

ok ok, more clickbait!

Once a week or two weeks depending on how often PRs are made I will be posting a short list of PRs that need to be reviewed or tested. Now that Travis has finally been implemented more effectively it should be far easier to determine whether the PRs at least compile on the *nix platforms, meaning the testing and reviewing should only need to be done.

Here are a couple of quick and easy ways to get hold of a single PR so that it can be built and tested, thanks to Timmy this has been reduced to just a few seconds of work.

How To

Method 1

find a PR you want to test, i'll use the sqlite one as an example.


if you add .patch to the end of the PR you get



you see a whole .patch text file in the browser window, save the page/file


i save mine to the root folder of my forked and cloned repo

assuming your branch is called development and it is on parity with the garagegames development branch, enter the following commands in gitbash or terminal launched from sourcetree. (i have a branch called gg-development specifically)


git checkout development

git branch TestPRs

git checkout TestPRs

git am 2299.patch


you should get somethimg like this.


I don't yet know about the whitespace issues, but it doesn't affect the testing, or at least not the ones I've done so far. I will adapt the instructions when i get more details

Method 2

you can clone a new repository directly to your computer just for testing.

once you have the clone you can issue the following commands

git fetch origin pull/2299/head:TestPRs
git checkout TestPRs


cleaning up ready for the next PR

Once you have reviewed and/or tested the PR, you can delete the branch using

git branch -d TestPRs


when this is done you are ready to start on the next PR.


This is quite a valuable service for torque, it means that JeffR doesn't need to do all the testing himself, even tho many of the PRs are by seasoned devs like Azaezel and Timmy they still need to be reviewed. This means bugs get fixed quicker, features get added faster; It also means Jeff Az and Timmy can focus their time where we the community and users need them most, working on the stuff we don't understand, but make the engine shiny shiny.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...