summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrancesco Borzì <borzifrancesco@gmail.com>2019-08-17 17:10:03 +0200
committerGitHub <noreply@github.com>2019-08-17 17:10:03 +0200
commit5aa7d424b9c2957d2be488355e1d0caad9ae3b20 (patch)
tree06b5fb185b556cd9a330663255a521081341ba3f
parent62b2afb56eb20e97c4f40e197c37faefabf0668f (diff)
downloadwiki-5aa7d424b9c2957d2be488355e1d0caad9ae3b20.tar.gz
wiki-5aa7d424b9c2957d2be488355e1d0caad9ae3b20.tar.bz2
wiki-5aa7d424b9c2957d2be488355e1d0caad9ae3b20.zip
Update The-Staging-Branch.md
-rw-r--r--docs/The-Staging-Branch.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/The-Staging-Branch.md b/docs/The-Staging-Branch.md
index cfc85e5..7281c5c 100644
--- a/docs/The-Staging-Branch.md
+++ b/docs/The-Staging-Branch.md
@@ -1,3 +1,5 @@
+# NOTE: CURRENTLY DISABLED
+
At AzerothCore, changes are submitted via PRs that are **first tested** and then merged to the `master`branch.
However, some PRs can be hard to test. For example when a PR contains changes that potentially can affect many things. To improve our QA and make sure such modifications don't introduce bugs in the master branch, we created the `staging` branch.
@@ -11,4 +13,4 @@ if you have a test server where you play just for fun, to try new things or do a
If you open an issue report with a bug that you've found in the `staging` branch, remember to mention in the report that you are using `staging` and not `master`.
-The staging branch is **not** meant to be used for changes that are straightforward to be tested, even if they are important changes. \ No newline at end of file
+The staging branch is **not** meant to be used for changes that are straightforward to be tested, even if they are important changes.