Contributing Guidelines
Thank you for your interest in contributing to the API Credential service! This document provides guidelines and instructions for contributing to the project.
Getting Started
- Fork the repository on GitHub
- Clone your fork locally
- Set up the development environment as described in the Setup Guide
- Create a new branch for your feature or bug fix
Development Workflow
-
Create a new branch from
main
for your changes -
Make your changes and ensure they follow the project's coding standards
- Write or update tests for your changes
-
Run the tests to ensure they pass
-
Format your code
-
Commit your changes with a descriptive commit message
-
Push your branch to your fork
-
Create a pull request from your fork to the main repository
Pull Request Guidelines
When submitting a pull request, please ensure:
- Your code follows the project's coding standards
- All tests pass
- Your changes are well-documented
- Your pull request has a descriptive title and detailed description
- Your pull request addresses only one issue or adds one feature
Coding Standards
- Follow PEP 8 style guidelines
- Use type hints for function parameters and return values
- Write docstrings for all functions, classes, and modules
- Keep functions small and focused on a single responsibility
- Use meaningful variable and function names
Testing
- Write unit tests for all new functionality
- Ensure all tests pass before submitting a pull request
- Aim for high test coverage
Documentation
- Update documentation for any changes to the API or functionality
- Document all new features, endpoints, and configuration options
- Keep the README and other documentation up to date
Versioning
We follow Semantic Versioning for this project:
- MAJOR version for incompatible API changes
- MINOR version for new functionality in a backward-compatible manner
- PATCH version for backward-compatible bug fixes
Issue Reporting
If you find a bug or have a feature request, please create an issue on GitHub:
- Check if the issue already exists
- Use a clear and descriptive title
- Provide detailed steps to reproduce the issue
- Include relevant logs, error messages, and screenshots
- Describe the expected behavior and the actual behavior
Code Review Process
All submissions require review. We use GitHub pull requests for this purpose:
- A maintainer will review your pull request
- They may request changes or improvements
- Once approved, a maintainer will merge your pull request
License
By contributing to this project, you agree that your contributions will be licensed under the project's LICENSE.
Questions?
If you have any questions or need help, please reach out to the maintainers or create an issue on GitHub.
Thank you for contributing to the API Credential service!