From 85863c66d01f3eea1b4386e0eac2ea76aee1f5cb Mon Sep 17 00:00:00 2001 From: it33 Date: Wed, 4 Nov 2015 08:23:37 -0800 Subject: Noting random build failures --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) (limited to 'CONTRIBUTING.md') diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index db8c90023..a6fcd8a78 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -46,5 +46,6 @@ git checkout -b - For example, for a ticket ID `PLT-394` start your comment with: `PLT-394:`. See [previously closed pull requests](https://github.com/mattermost/platform/pulls?q=is%3Apr+is%3Aclosed) for examples 3. Once submitted, your pull request will be checked via an automated build process and will be reviewed by at least two members of the Mattermost core team, who may either accept the PR or follow-up with feedback. It would then get merged into `master` for the next release + 4. If the build fails, check the error log to narrow down the reason. Sometimes one of the multiple build tests will randomly fail, potentially due to race conditions, so if you see just one build failure and can't find an obvious error message try re-running the build. 4. If you've included your mailing address in Step 1, you'll be receiving a [Limited Edition Mattermost Mug](http://forum.mattermost.org/t/limited-edition-mattermost-mugs/143) as a thank you gift after your first pull request has been accepted -- cgit v1.2.3-1-g7c22