|
| 1 | +# Contributing to Python-Pin-Payments Library |
| 2 | + |
| 3 | +First off, thank you for considering contributing to Python-Pin-Payments Library! It's people like you that make this project great! |
| 4 | + |
| 5 | +## Code of Conduct |
| 6 | + |
| 7 | +This project and everyone participating in it is governed by the [Python-Pin-Payments Library Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [viacheslav.lisovoi@onix-systems.com](mailto:viacheslav.lisovoi@onix-systems.com). |
| 8 | + |
| 9 | +## How Can I Contribute? |
| 10 | + |
| 11 | +### Reporting Bugs |
| 12 | + |
| 13 | +This section guides you through submitting a bug report for Python-Pin-Payments Library. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports. |
| 14 | + |
| 15 | +#### Before Submitting A Bug Report |
| 16 | + |
| 17 | +- **Perform a cursory search** to see if the bug has already been reported. If it has and the issue is still open, add a comment to the existing issue instead of opening a new one. |
| 18 | + |
| 19 | +#### How Do I Submit A (Good) Bug Report? |
| 20 | + |
| 21 | +Bugs are tracked as GitHub issues. After you've determined that a bug hasn't been filed, create an issue and provide the following information by filling in the template. |
| 22 | + |
| 23 | +- **Use a clear and descriptive title** for the issue to identify the problem. |
| 24 | +- **Describe the exact steps** which reproduce the problem in as many details as possible. |
| 25 | +- **Provide specific examples** to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. |
| 26 | +- **Describe the behavior you observed** after following the steps and point out what exactly is the problem with that behavior. |
| 27 | +- **Explain which behavior you expected to see** instead and why. |
| 28 | +- **Include screenshots** which show you following the described steps and clearly demonstrate the problem. |
| 29 | +- **If you're reporting that the library crashed**, include a crash report with a stack trace from the program. |
| 30 | +- **If the problem is related to performance**, include a CPU profile capture of the execution of the affected functions. |
| 31 | + |
| 32 | +### Suggesting Enhancements |
| 33 | + |
| 34 | +This section guides you through submitting an enhancement suggestion for Python-Pin-Payments Library, including completely new features and minor improvements to existing functionality. |
| 35 | + |
| 36 | +#### Before Submitting An Enhancement Suggestion |
| 37 | + |
| 38 | +- **Perform a cursory search** to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. |
| 39 | + |
| 40 | +#### How Do I Submit A (Good) Enhancement Suggestion? |
| 41 | + |
| 42 | +Enhancement suggestions are tracked as GitHub issues. After you've determined that the enhancement hasn't been filed, create an issue and provide the following information: |
| 43 | + |
| 44 | +- **Use a clear and descriptive title** for the issue to identify the suggestion. |
| 45 | +- **Provide a step-by-step description of the suggested enhancement** in as much detail as possible. |
| 46 | +- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. |
| 47 | +- **Include screenshots and code snippets** which demonstrate the use of the suggested enhancement. |
| 48 | + |
| 49 | +### Your First Code Contribution |
| 50 | + |
| 51 | +- **Get started with our documentation**: follow the setup instructions in the README.md file. |
| 52 | +- **Check for open issues**: start by looking through the [issues](https://github.com/yourusername/python-pin-payments/issues). |
| 53 | + |
| 54 | +### Pull Requests |
| 55 | + |
| 56 | +The process described here has several goals: |
| 57 | + |
| 58 | +- Maintain the project's quality |
| 59 | +- Fix problems that are important to users |
| 60 | +- Engage the community in working toward the best possible Python-Pin-Payments Library |
| 61 | +- Enable a sustainable system for maintainers to review contributions |
| 62 | + |
| 63 | +Please follow these steps to have your contribution considered by the maintainers: |
| 64 | + |
| 65 | +1. **Create a branch** for your contribution. |
| 66 | +2. **Write tests** for your changes. |
| 67 | +3. **If you added code that should be tested, add tests**. |
| 68 | +4. **Ensure the test suite passes**. |
| 69 | +5. **Make sure your code lints**. |
| 70 | +6. **Submit a pull request** through the GitHub. |
| 71 | + |
| 72 | +Code Style |
| 73 | +---------- |
| 74 | + |
| 75 | +- Follow the [PEP 8](https://www.python.org/dev/peps/pep-0008/) style guide. |
| 76 | +- Ensure that the code passes all linting checks. |
| 77 | + |
| 78 | +Tests |
| 79 | +----- |
| 80 | + |
| 81 | +- Use [pytest](https://pytest.org/) for testing. |
| 82 | +- Ensure all tests pass before submitting a pull request. |
| 83 | + |
| 84 | +Licensing |
| 85 | +--------- |
| 86 | + |
| 87 | +By contributing to Python-Pin-Payments Library, you agree that your contributions will be licensed under the MIT License. |
0 commit comments