aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAokromes <Aokromes@users.noreply.github.com>2014-10-19 11:41:13 +0200
committerAokromes <Aokromes@users.noreply.github.com>2014-10-19 11:41:13 +0200
commitda67ef9c997f126405bd16e58c429b3efc5de844 (patch)
treede7ad030e29c39bd324acefa8ec814c8490d9727
parent0bf163bf8fae3d9fc0f116964f5420d8875c2623 (diff)
Update CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d702132a277..52b6ed42972 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -14,6 +14,7 @@ When creating patches read:
- [WDB Fields](http://www.trinitycore.org/f/topic/58-wdb-fields/)
- [Git Squash](https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/)
- [SQL Guidelines](http://collab.kpsn.org/display/tc/SQL+Guidelines)
+
We suggest you to create one branch for each `C++` based fix: on that way you can continue creating more fixes without having to wait to get one pull request merged.
For the `SQL` files of `C++` based fixes the naming schema is: `YYYY_MM_DD_i_database_description.sql`, where `YYYY_MM_DD` is the date of the fix, `i_database` is the *ith* sql created that day for `database`.
When doing changes to `auth` or `characters` database remember to update the base files (`/sql/base/*`).