From 2b4ed1d70e981beb844425fb79ca52d401aa9ed7 Mon Sep 17 00:00:00 2001
From: Azareal <azareal@users.noreply.github.com>
Date: Mon, 30 Jul 2018 18:09:08 +1000
Subject: [PATCH] Those tests were too thorough, even reaching into sections
 which aren't quite implemented. Added new rules for commits which introduced
 database changes.

---
 CONTRIBUTING.md | 2 ++
 run-linux-tests | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 74d7fff7..9185631f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -24,6 +24,8 @@ Try to use the single responsibility principle where ever possible, with the exc
 
 Avoid hand-rolling queries. Use the builders, a ready built statement or a datastore structure instead. Preferably a datastore.
 
+Commits which require the patcher / update script to be run should be prefixed with "Database Changes: "
+
 More coming up.
 
 # JavaScript
diff --git a/run-linux-tests b/run-linux-tests
index 918f8ae2..1e50e6a4 100644
--- a/run-linux-tests
+++ b/run-linux-tests
@@ -1,4 +1,4 @@
 echo "Generating the dynamic code"
 go generate
 echo "Running tests"
-go test -coverprofile c.out ./...
+go test -coverprofile c.out