diff options
| author | Aokromes <Aokromes@users.noreply.github.com> | 2014-10-19 05:09:34 +0200 |
|---|---|---|
| committer | Aokromes <Aokromes@users.noreply.github.com> | 2014-10-19 05:09:34 +0200 |
| commit | d682b571d3c47278ce1be0fcea241e08ee52ae61 (patch) | |
| tree | 2c83c83c58364b00fade285c8a665fe1bb5072b6 | |
| parent | 98f98fa17fde4a1294b3e9227973ce5df70fbd6b (diff) | |
Update CONTRIBUTING.md
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 99fb588c1cf..d702132a277 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -13,7 +13,7 @@ When creating patches read: - [TrinityCore Development Standards](http://www.trinitycore.org/f/topic/6-trinitycore-developing-standards/) - [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/*`). |