DB/Quest: Suspicious Hoofprints (Horde Version)
[trinitycore] / CONTRIBUTING.md
1 # Contributing
2
3 So, you want to contribute? Great!
4 Contributing is not only about creating fixes, but also reporting bugs. Before reporting a bug, please make sure to use the latest core and database revision.
5
6
7 Issues
8 ======
9
10 Read [this](https://www.trinitycore.org/f/topic/37-the-trinitycore-issuetracker-and-you/) before creating a ticket.
11 If you have problems with TrinityCore installation, read [this](https://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/).
12
13 Mandatory things when creating a ticket:
14 ========================================
15
16 - Branch
17 - commit hash (if you get something like TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch) (Win64, Release), please read this [post](https://www.trinitycore.org/f/topic/345-howto-properly-install-git-on-windows-fix-trinitycore-rev-1970-01-01-000000-0000/) or clone this repository instead downloading the source code.
18 - entries of affected creatures / items / quests with a link to the relevant wowhead page.
19 - clear title and description of the bug - if your english is very bad, please use google translate or yandex to translate to english and include one text in your native language.
20
21 When reporting a crash, you MUST compile in debug mode because release dumps are useless (not enough information) - if you don't know how to compile in debug, read [this](https://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry47672)
22
23 We sugest the title and body to have the next style:
24
25 DB/Quest: The Collapse
26
27 4.3.4 branch
28 hash 63f96a282307
29 The quest "The Collapse" http://www.wowhead.com/quest=11706 lacks final event.
30
31 Creating Pull Requests:
32 =======================
33
34 1. Fork it.
35 2. Create a branch (`git checkout -b fixes`) (Note: fixes is an arbitrary name, choose whatever you want here)
36 3. Commit your changes (`git commit -am "Added Snarkdown"`)
37 4. Push to the branch (`git push origin fixes`)
38 5. Open a Pull Request
39
40
41 When creating patches read:
42 - [TrinityCore Development Standards](https://www.trinitycore.org/f/topic/6-trinitycore-developing-standards/)
43 - [WDB Fields](https://www.trinitycore.org/f/topic/58-wdb-fields/)
44 - [Git Squash](https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/)
45
46
47 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.
48 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`.
49 When doing changes to `auth` or `characters` database remember to update the base files (`/sql/base/*`).
50 For SQL only fixes, please [create a ticket](https://github.com/TrinityCore/TrinityCore/issues/new).
51 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
52
53 Wiki
54 ====
55
56 The wiki is located at [https://trinitycore.info](https://trinitycore.info).
57
58 You are welcome to create an account and help us improve and extend the wiki.
59
60
61 Requirements
62 ============
63
64
65 Software requirements are available in the [wiki](https://www.trinitycore.info/display/tc/Requirements) for
66 Windows, Linux and Mac OSX.
67
68
69 If you choose Linux, we recommend to use Debian 8, since it's the Linux that we use to test compilations.