custom-post-type-permalinks
Last commit date
CPTP
7 years ago
assets
8 years ago
language
8 years ago
CONTRIBUTING.md
9 years ago
CPTP.php
8 years ago
LICENSE
9 years ago
custom-post-type-permalinks.php
7 years ago
readme.md
7 years ago
readme.txt
7 years ago
screenshot-1.png
14 years ago
CONTRIBUTING.md
25 lines
| 1 | # How to contribute |
| 2 | |
| 3 | ## Getting Started |
| 4 | |
| 5 | * Make sure you have a [](https://github.com/signup/freeGitHub account](https://github.com/signup/free](https://github.com/signup/free) |
| 6 | * Submit a ticket for your issue, assuming one does not already exist. |
| 7 | * Clearly describe the issue including steps to reproduce when it is a bug. |
| 8 | * Make sure you fill in the earliest version that you know has the issue. |
| 9 | * Fork the repository on GitHub |
| 10 | |
| 11 | ## Making Changes |
| 12 | |
| 13 | * Create a topic branch from where you want to base your work. |
| 14 | * This is usually the master branch. |
| 15 | * Only target release branches if you are certain your fix must be on that |
| 16 | branch. |
| 17 | * To quickly create a topic branch based on master; `git checkout -b |
| 18 | fix/master/my_contribution master`. Please avoid working directly on the |
| 19 | `master` branch. |
| 20 | * Make commits of logical units. |
| 21 | * Check for unnecessary whitespace with `git diff --check` before committing. |
| 22 | * Make sure your commit messages are in the proper format. |
| 23 | |
| 24 | By contributing code, you grant its use under the [](http://www.gnu.org/licenses/gpl-2.0.htmlGNU General Public License v2 (or later)](http://www.gnu.org/licenses/gpl-2.0.html](http://www.gnu.org/licenses/gpl-2.0.html). |
| 25 |