diff options
| author | jackpoz <giacomopoz@gmail.com> | 2021-07-04 11:43:02 +0200 |
|---|---|---|
| committer | jackpoz <giacomopoz@gmail.com> | 2021-07-04 11:43:02 +0200 |
| commit | 0f26daafbf99c3bd77bcf9dbd34f8d6121d444b5 (patch) | |
| tree | b6a2cc38eb0be8a0bfd0ced7075bb0e6d6e6cbc3 | |
| parent | ed43294e2d599ab02643ddc0a93df406d1cf5c64 (diff) | |
GitHub: Update link to create new issues
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 99d3cfe22c3..754aa3cc71f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,7 +47,7 @@ When creating patches read: We suggest that you create one branch for each C++ based fix: this will allow you to create more fixes without having to wait for your pull request to be merged. For the SQL files coming with C++ based fixes the naming schema is `YYYY_MM_DD_i_database.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/*`). -For SQL only fixes, please [create a ticket](https://github.com/TrinityCore/TrinityCore/issues/new). +For SQL only fixes, please [create a ticket](https://github.com/TrinityCore/TrinityCore/issues/new/choose). Since it's very unlikely that your Pull Request will be merged on the day that you open it, please name the files with an impossible date to avoid merging issues ie: 2015_13_32_00_world.sql Wiki |