Thank you for contributing to WebsiteUtils!
We welcome your pull requests (PRs). For minor fixes (e.g., documentation improvements), feel free to submit a PR directly. If you would like to implement a new feature or a bug, please make sure you (or someone else) has opened an appropriate issue first; in your PR, please mention the issue it addresses.
- Fork this repository.
- Make your code changes locally.
- Check the style using pylint and black:
- install pylint-badge:
pip install git+https://github.com/blengerich/pylint-badge pylint-badge WebsiteUtils pylint.svgcalculates the current pylint score.black --check WebsiteUtils --target-version=py38gives a list of files to be updated by black.- Picking a particular file
foo.pyfrom the list above, I runblack WebsiteUtils/foo.py --target-version=py38. This makes formatting changes to align with the Black style. - Manually inspect the changes with
git diff WebsiteUtils/foo.py. - Re-run
pylint-badge WebsiteUtils pyling.svgto re-calculate the pylint score, and re-create a badge with that score. Sanity check that pylint score did not decrease by making style changes with black.
- install pylint-badge:
- (Optional) Include your name in alphabetical order in ACKNOWLEDGEMENTS.md.
- Issue a PR to merge your changes.
We use GitHub issues to track bugs and feature requests. Before submitting an issue, please make sure:
- You have read the README and your question is NOT addressed there.
- You have done your best to ensure that your issue is NOT a duplicate of one of the previous issues.
- Your issue is either a bug (unexpected/undesirable behavior) or a feature request. If it is just a question, please ask it in the Discussions forum.
When submitting an issue, please make sure to use the appropriate template.
By contributing to WebsiteUtils, you agree that your contributions will be licensed under the LICENSE file in the root directory of the source tree.