Skip to content

Latest commit

 

History

History
65 lines (30 loc) · 3.94 KB

CONTRIBUTING.md

File metadata and controls

65 lines (30 loc) · 3.94 KB

How to contribute to Search Engine Parser

All Contributions to the code base or documentation must be done on a branch with intuitive name e.g aol-#13-patch, yandex-engine-implementation

Did you find a bug?

  • Ensure the bug was not already reported by searching on GitHub under Issues.

  • If you're unable to find an open issue addressing the problem, open a new one. If possible, be sure to make use of the bug template with label bug

  • Ensure the issue description clearly describes the bug.Include the relevant issue number if applicable.

Did you write a patch that fixes a bug?

  • Ensure the bug is first reported by searching on GitHub under Issues using label bug

  • If issue does not exist, open an issue with the bug report template

  • Open a new GitHub pull request with the patch using bug fix template.

  • Ensure the PR description clearly describes the solution. Include the relevant issue number if applicable.

Do you intend to add a new feature or change an existing one?

  • Ensure the feature was not already requested by searching on GitHub under Issues. Search using the enhancement or feature labels

  • Suggest your feature/change in the search-engine-parser mailing list and start writing code.

  • Do not open an issue on GitHub until you have collected positive feedback about the change.

  • Raise an issue using the feature request template with labels enhancement

  • Upon implementing the feature, make a PR using the feature implementation template

Engines

Do you have questions about the source code?

Do you want to contribute to the search-engine-parser documentation?

NOTE: There are exceptions in every case and we know that too!

SearchEngineParser is a volunteer effort. We encourage you to pitch in and join the team!

Thanks!

Bisoncorps Team - Building Interesting Software Opensourced for humaNS ❤️ ❤️