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
[SYNC] branch 'fix-lowercase-files-208' with 'dev-v5.6'
* dev-v5.6:
[STYLE] Cleanup fixes from GHI #208 for release
[STYLE] Cleanup fixes from GHI #292 for release
[DOCUMENTATION] Update documentation and configs to match
[DOCUMENTATION] Create SECURITY.md
[FIX] Resolve regression in tests due to abbriviations in updated packages (- WIP #292 -)
[FIX] resolve flaky test_different_python with improved diognostics (- WIP GHI #292 -)
[FIX] resolve regression for test_fail_on_partial_match (- WIP GHI #292 -)
[FIX] resolve regression for test_allow_only_partial (- WIP GHI #292 -)
[DEBUG] revert some unstable changes to makefile
Bump cryptography from 46.0.2 to 46.0.5
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,17 +13,26 @@ The design policy of `pip-licenses` is as follows.
13
13
14
14
1. Fork this repository on your GitHub account.
15
15
2. Create a branch to represent changes.
16
-
* Branch name does **NOT** need `feature/` prefix. Because git-flow is too complicated.
17
-
3. Create a new venv environment.
18
-
4. Install package for development via `make setup` .
16
+
* Branch name does **NOT** need `feature/` prefix. Because git-flow is configured differently for maintainers.
17
+
3. Create a new venv environment and Install package for development via `make setup` .
19
18
* Dependencies are managed by [pip-tools](https://pypi.org/project/pip-tools/).
20
-
* If you want to add dependency packages for development, edit [dev-requirements.in](https://github.com/raimon49/pip-licenses/blob/master/dev-requirements.in) file and run `make update-depends` .
21
-
*When you want to install the code under development, run `make local-install` .
19
+
* If you want to add dependency packages for development, edit [the dev entry in pyproject.toml](https://github.com/raimon49/pip-licenses/blob/master/pyproject.toml) file and run `make update-depends` .
20
+
*If you want to install the code under development, run `make local-install` .
22
21
23
22
## Implementation and testing
24
23
25
-
*`pip-licenses` always measures code coverage for code quality. If you implement the new feature, please also write unit test in [test\_piplicenses.py](https://github.com/raimon49/pip-licenses/blob/master/test_piplicenses.py).
24
+
*`pip-licenses` always measures code coverage for code quality. If you implement a new feature, please also write unit test in [test\_piplicenses.py](https://github.com/raimon49/pip-licenses/blob/master/test_piplicenses.py).
26
25
* Tests can be run with `make test` .
27
26
* Code conventions follow the [PEP 8](https://www.python.org/dev/peps/pep-0008/).
28
27
* You can format the code by running `make lint` .
29
-
* Send pull request to master branch.
28
+
* Send pull request to master branch. Maintainer(s) may adjust PRs to the appropriate development branch as realevant.
29
+
30
+
## Security policy
31
+
32
+
If you find a significant vulnerability, or evidence of one, please report it privately.
33
+
34
+
* We prefer that you use the
35
+
[GitHub mechanism for privately reporting a vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability).
If you find a significant vulnerability, or evidence of one, please report it privately.
4
+
5
+
* We prefer that you use the
6
+
[GitHub mechanism for privately reporting a vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability).
0 commit comments