Skip to content

Latest commit

 

History

History
43 lines (28 loc) · 2.52 KB

CONTRIBUTING.md

File metadata and controls

43 lines (28 loc) · 2.52 KB
Raw

Contributing to ProxyScraper

First off, thank you for considering contributing to ProxyScraper. Your help is essential for keeping this project active and improving its quality.

The following is a set of guidelines for contributing to ProxyScraper. These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request if you believe something should be added, removed, or modified. Code of Conduct

This project and everyone participating in it are governed by our Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [[email protected]]. How Can I Contribute? Reporting Bugs

Before submitting a bug report, please ensure that:

  • You have searched the existing issues to see if the issue has already been reported.
  • You are using the latest version of ProxyScraper and have checked if the issue still exists in the latest release.

If you didn't find an existing issue addressing the problem, feel free to open a new issue. When reporting a bug, please provide detailed information, including steps to reproduce the issue. Suggesting Enhancements

If you have ideas for enhancements or new features, you can open a new issue to discuss them. Be clear and provide as much context as possible to facilitate constructive discussions. Pull Requests

We welcome pull requests to fix bugs, add new features, or improve documentation. If you're unsure about whether a specific change is appropriate, feel free to open an issue to discuss it before starting work on the pull request.

To contribute via pull requests, follow these steps:

  • Fork the repository and create your branch from master.
  • Make your changes, ensuring they adhere to the style guidelines.
  • Test your changes thoroughly.
  • Ensure your commits are well-described and atomic.
  • Open a pull request, providing a clear description of your changes and referencing any related issues.

Style Guidelines

To maintain a consistent codebase, please adhere to the following style guidelines:

  • Use clear and descriptive variable and function names.
  • Follow the existing code formatting and naming conventions.
  • Write clear, concise, and helpful comments.

License

By contributing to ProxyScraper, you agree that your contributions will be licensed under the MIT License.