|
2 | 2 |
|
3 | 3 | Follow these guidelines if you'd like to contribute to the project! |
4 | 4 |
|
5 | | ---- |
6 | 5 |
|
7 | | -## Table of contents |
8 | | - |
9 | | -Read through these guidelines before you get started: |
10 | | - |
11 | | -1. [Questions & Concerns](#questions--concerns) |
12 | | -2. [Issues & Bugs](#issues--bugs) |
13 | | -3. [Feature Requests](#feature-requests) |
14 | | -4. [Submitting Pull Requests](#submitting-pull-requests) |
15 | | -5. [Code Style](#code-style) |
16 | | - |
17 | | -## Questions & concerns |
| 6 | +## Questions |
18 | 7 |
|
19 | 8 | If you have any questions about using or developing for this project, reach out to @bugfishtm. |
20 | 9 |
|
21 | | -## Issues & bugs |
| 10 | +## Issues |
22 | 11 |
|
23 | 12 | Submit an issue or pull request with a fix if you find any bugs in |
24 | | -the project. When submitting an issue or pull request, make sure you're as detailed as possible and fill in all answers to questions asked in the templates. For example, an issue that simply states "X/Y/Z isn't working!" will be closed. |
25 | | - |
26 | | -## Feature requests |
27 | | - |
28 | | -Submit an issue to request a new feature. Features fall into one of two |
29 | | -categories: |
30 | | - |
31 | | -1. **Major**: Major changes should be discussed via email. I'm |
32 | | - always open to suggestions and will get back to you as soon as I can! |
33 | | -2. **Minor**: A minor feature can simply be added via a pull request. |
34 | | - |
35 | | -## Submitting pull requests |
36 | | - |
37 | | -Before you do anything, make sure you check the current list of pull requests |
38 | | -to ensure you aren't duplicating anyone's work. Then, do the following: |
| 13 | +the project. When submitting an issue or pull request, make sure you're as detailed as possible. |
39 | 14 |
|
40 | | -1. Fork the repository and make your changes in a git branch: `git checkout -b my-branch base-branch` |
41 | | -2. Read and follow the code style guidelines. |
42 | | -3. Make sure your feature or fix doesn't break the project! Test thoroughly. |
43 | | -4. Commit your changes, and be sure to leave a detailed commit message. |
44 | | -5. Push your branch to your forked repo on GitHub: `git push origin my-branch` |
45 | | -6. Submit a pull request and hold tight! |
46 | | -7. If any changes are requested by the project maintainers, make them and follow this process again until the changes are merged in. |
| 15 | +## Features |
47 | 16 |
|
48 | | -## Code style |
| 17 | +Submit an issue to request a new feature. |
49 | 18 |
|
50 | | -Please mark your changes by comments inside the code structure. |
| 19 | +🐟 Bugfish <3 |
0 commit comments