CraftBukkit
Public
Commits
md_5 authored ee7116b4cc3
| 3 3 | ##### Pull Request Title Example |
| 4 4 | The first line in a Pull Request(PR) message is an imperative statement briefly explaining what the PR is achieving. |
| 5 5 | If the PR fixes a bug, or implements a new feature as requested from the [JIRA](http://hub.spigotmc.org/jira/), then it should reference that ticket. |
| 6 6 | This is accomplished by simply type SPIGOT-####, where #### is the ticket number. (i.e. SPIGOT-3510). |
| 7 7 | You can reference multiple tickets in a single commit message; for example: "SPIGOT-1, SPIGOT-2" without the quotes. |
| 8 8 | |
| 9 9 | __For Example:__ |
| 10 10 | * SPIGOT-3510: Velocity broken for certain entities |
| 11 11 | * MC-111753, SPIGOT-2971: Brewing stand not reloading |
| 12 12 | |
| 13 - | As you can see, Minecraft tickets can be referenced by including the appropriate ticket number (i.e. MC-111753) |
| 13 + | As you can see, Minecraft tickets can be referenced by including the appropriate ticket number (i.e. MC-111753). |
| 14 + | Where a pull request is spread across multiple repositories, please keep the title and first line of the commit message the same for each. |
| 14 15 | |
| 15 16 | ##### Pull Request Message Expectations |
| 16 17 | The body of a PR needs to describe how the ticket was resolved, or if there was no ticket, describe the problem itself. |
| 17 18 | If a PR is for both Bukkit and CraftBukkit it should include a link to the appropriate PR. [Read this to learn how to link to a PR.](https://confluence.atlassian.com/bitbucketserver053/markdown-syntax-guide-938022413.html?utm_campaign=in-app-help&utm_medium=in-app-help&utm_source=stash#Markdownsyntaxguide-Linkingtopullrequests) |
| 18 19 | |
| 19 20 | ##### Submitting the Changes |
| 20 21 | * Push your changes to a topic branch in your fork of the repository. |
| 21 22 | * Submit a pull request to the relevant repository in the Spigot organization. |
| 22 23 | * Make sure your pull request meets our [code requirements.](README.md) |
| 23 24 | * If you are fixing a JIRA ticket, be sure to update the ticket with a link to the pull request. |