-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCONTRIBUTING
58 lines (42 loc) · 2.49 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
First of all, thank you for taking an interest.
# Introduction
Please take some time to read and understand this file. This will help keep the project clean and transparent for all contributors. It will also make it easier for admins and moderators to merge your code suggestions.
# Forks
The first part is to create your own fork of the project. You can do this directly from GitHub by pressing the fork button in the top right corner. This will create a copy of the repository on your account. In this repository you can do whatever you want without it affecting the original repository. As long as you adhere to the following rules when branching and creating pull requests (PR).
# Branches
When creating a new branch please adhere to the following guidelines:
- The branch should match one of the below
- The branch "sections" are seperated with "/" (slash)
- The branch name is lowercase
## Issue fixing branch
If the branch you are creating fixes an issue please name the branch:
`issue/(Issue #)/(GitHub name)`
This signals that the branch is trying to fix a known issue.
## Feature branch
If you would like to add a new feature that you feel is missing. Please create a feature-request issue on the original repository, this way a issue number gets created. Then create the branch with the name:
`feature/(Issue #)/(GitHub name)`
## Examples
**Issue:**
`issue/18/vitexftw`
**Feature:**
`feature/22/Mads`
# Commit messages
Commit messages should be consice and descriptive. They should specify what section was changed.
Please prefix your commit messeage with one of the following.
| Prefix | Description |
|:------------|:---------------------------|
| fix: | Fixes a GitHub issue |
| feat: | Adds new feature |
| doc: | Document code/github |
| refactor: | Rewritten code (no effect) |
### Example
See commit messeage for this PR [#17](https://github.com/ViTeXFTW/ZeroSyntax-Server/pull/17)
"Fix: [BUG] Incorrect error in WeaponSet Weapon property #14"
# Pull Requests (PR)
For PRs please use the attached [PR Template](./.github/PULL_REQUEST_TEMPLATE/pull_request_template.md)
### Example
See commit messeage for this PR [#17](https://github.com/ViTeXFTW/ZeroSyntax-Server/pull/17)
# Merges
Merges are only approved by the admin (ViTeXFTW), and will be done when the PR has been reviewed and tested.
# License
By contributing you agree that your code will be licensed under the [LICENSE](./LICENSE) file in the root directory of this source tree.