-
Notifications
You must be signed in to change notification settings - Fork 0
/
CONTRIBUTING
56 lines (39 loc) · 2.67 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
# Contributing to CodeBin
First of all, thank you for considering contributing to CodeBin! Your help and support will make this project even better. This document provides a set of guidelines for contributing to CodeBin. Please read and follow these guidelines to ensure a smooth and effective contribution process.
## Code of Conduct
By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please ensure that you treat everyone with respect and professionalism.
## How to Contribute
There are several ways you can contribute to CodeBin:
1. Reporting bugs
2. Suggesting new features or enhancements
3. Submitting bug fixes
4. Implementing new features
5. Improving documentation
6. Reviewing and testing pull requests
### Reporting Bugs
If you've found a bug, please create an issue in the GitHub repository with the following information:
1. A clear and concise description of the bug
2. Steps to reproduce the bug
3. Any relevant logs or error messages
4. Your environment (OS, browser, etc.)
5. Possible solutions or workarounds, if any
### Suggesting Features or Enhancements
We're always looking for ways to improve CodeBin. If you have an idea for a new feature or enhancement, please create an issue in the [GitHub repository](https://github.com/TheNolle/CodeBin/issues) with the following information:
1. A clear and concise description of the feature or enhancement
2. Why you think it would be useful
3. Any relevant mockups, prototypes, or examples
4. How the feature or enhancement could be implemented
### Submitting a Pull Request
If you'd like to submit a pull request, please follow these steps:
1. Fork the repository.
2. Create a new branch with a descriptive name.
3. Make your changes in the new branch.
4. Commit your changes and write a descriptive commit message.
5. Push your changes to your forked repository.
6. Open a pull request, and your changes will be reviewed and potentially merged!
Please ensure that your code follows the existing style and conventions of the project. Additionally, make sure to test your changes thoroughly before submitting your pull request.
### Testing and Code Quality
To ensure the stability and quality of the project, please make sure to test your changes thoroughly. Additionally, it's a good idea to use linters and other code quality tools to help maintain a consistent coding style.
## Getting Help
If you have any questions or need assistance, please reach out to the community on our [Discord server](https://discord.com/invite/86yVsMVN9z). We're here to help and support your contributions!
Once again, thank you for considering contributing to CodeBin! Together, we can make this project even better.