Developers guide

Joachim Metz edited this page Nov 25, 2015 · 6 revisions


We love contributions! If you're contributing artifacts, please follow the Style Guide and make sure the tests pass:

$ python

If you're contributing python code, check with us on the mailing list first, especially if it's something big.

We use the github fork and pull review process to review all contributions. First, fork the artifact repository by following the github instructions. Then check out your personal fork:

git clone

Add an upstream remote so you can easily keep up to date with the main repository:

git remote add upstream

To update your local repo from the main:

git pull upstream master

Make your changes and once you're ready for review, commit them to your personal fork and then use the GitHub Web UI to create and send the pull request. We'll review and merge the change.

Adding new artifact labels

An artifact definition can contain one or more labels. For the validation these labels defined in artifacts/ in LABELS.

At the moment when a new label is added make sure to add the same label to lib/ of the GRR project in ARTIFACT_LABELS.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.