mirror of
https://github.com/TrinityCore/TrinityCore.git
synced 2026-01-16 07:30:42 +01:00
f709d77ed6
Apply general writing codestyle for GitHub Pull Requests: - move the "Closes #" text down to its own line, as GitHub prefers to read the git command without preceding text. - move the text "(Does it build, tested in-game, etc.)" down to a new line to indicate where we want the info inserted.
37 lines
765 B
Markdown
37 lines
765 B
Markdown
<!--- (**********************************)
|
|
(** Fill in the following fields **)
|
|
(**********************************) --->
|
|
|
|
**Changes proposed:**
|
|
|
|
-
|
|
-
|
|
-
|
|
|
|
**Target branch(es):** 3.3.5/master
|
|
|
|
- [ ] 3.3.5
|
|
- [ ] master
|
|
|
|
**Issues addressed:**
|
|
|
|
Closes # (insert issue tracker number)
|
|
|
|
|
|
**Tests performed:**
|
|
|
|
(Does it build, tested in-game, etc.)
|
|
|
|
|
|
**Known issues and TODO list:** (add/remove lines as needed)
|
|
|
|
- [ ]
|
|
- [ ]
|
|
|
|
|
|
<!--- Notes
|
|
- Enable the setting "[√] Allow edits from maintainers." when creating your pull request.
|
|
- If this PR only contains SQL files, open a new issue instead and post or link the SQL in the issue.
|
|
- When adding new SQL files, name them 9999_99_99_99_db_name.sql to reduce the chance of possible merge conflicts.
|
|
--->
|