summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorit33 <iantien@gmail.com>2015-11-04 08:23:37 -0800
committerit33 <iantien@gmail.com>2015-11-04 08:23:37 -0800
commit85863c66d01f3eea1b4386e0eac2ea76aee1f5cb (patch)
tree56100402fe097684719ff7c46e2ac483351c8719 /CONTRIBUTING.md
parente1fef658012f08dc4b093417b27faa9cf6dc609f (diff)
downloadchat-85863c66d01f3eea1b4386e0eac2ea76aee1f5cb.tar.gz
chat-85863c66d01f3eea1b4386e0eac2ea76aee1f5cb.tar.bz2
chat-85863c66d01f3eea1b4386e0eac2ea76aee1f5cb.zip
Noting random build failures
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md1
1 files changed, 1 insertions, 0 deletions
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 <branch name>
- 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