You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# This workflow will upload a Python Package using Twine when a release is created
2
+
# For more information see: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries
3
+
4
+
# This workflow uses actions that are not certified by GitHub.
5
+
# They are provided by a third-party and are governed by
6
+
# separate terms of service, privacy policy, and support
- In general, contributors should make code changes on a branch, and then [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have the changes merged
4
+
- It is strongly recommended that contributors work on code changes in an isolated Python environment
5
+
+ Use `pip install -e .` to install this library locally, so that any local code changes are reflected immediately in your current Python environment
6
+
- To make sure your code style is compliant, run `./run_linting.sh` locally on your computer to check style violations
7
+
+ You might want to run `chmod +x run_linting.sh` to make `run_linting.sh` executable
8
+
- Please also run all unit tests by running `./run_tests.sh` before committing code to GitHub
9
+
+ You might want to run `chmod +x run_tests.sh` to make `run_tests.sh` executable
10
+
- Even if you don't run unit tests and check code styles locally, unit tests and code styles are checked on every push at GitHub
0 commit comments