| Name | conventional-pre-commit JSON |
| Version |
3.2.0
JSON |
| download |
| home_page | None |
| Summary | A pre-commit hook that checks commit messages for Conventional Commits formatting. |
| upload_time | 2024-03-29 17:40:12 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
git
pre-commit
conventional-commits
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# conventional-pre-commit
A [`pre-commit`](https://pre-commit.com) hook to check commit messages for
[Conventional Commits](https://conventionalcommits.org) formatting.
Works with Python >= 3.8.
## Usage
Make sure `pre-commit` is [installed](https://pre-commit.com#install).
Create a blank configuration file at the root of your repo, if needed:
```console
touch .pre-commit-config.yaml
```
Add a new repo entry to your configuration file:
```yaml
repos:
# - repo: ...
- repo: https://github.com/compilerla/conventional-pre-commit
rev: <git sha or tag>
hooks:
- id: conventional-pre-commit
stages: [commit-msg]
args: []
```
Install the `pre-commit` script:
```console
pre-commit install --hook-type commit-msg
```
Make a (normal) commit :x::
```console
$ git commit -m "add a new feature"
[INFO] Initializing environment for ....
Conventional Commit......................................................Failed
- hook id: conventional-pre-commit
- duration: 0.07s
- exit code: 1
[Bad Commit message] >> add a new feature
Your commit message does not follow Conventional Commits formatting
https://www.conventionalcommits.org/
Conventional Commits start with one of the below types, followed by a colon,
followed by the commit message:
build chore ci docs feat fix perf refactor revert style test
Example commit message adding a feature:
feat: implement new API
Example commit message fixing an issue:
fix: remove infinite loop
Example commit with scope in parentheses after the type for more context:
fix(account): remove infinite loop
Example commit with a body:
fix: remove infinite loop
Additional information on the issue caused by the infinite loop
```
Make a (conventional) commit :heavy_check_mark::
```console
$ git commit -m "feat: add a new feature"
[INFO] Initializing environment for ....
Conventional Commit......................................................Passed
- hook id: conventional-pre-commit
- duration: 0.05s
```
## Install with pip
`conventional-pre-commit` can also be installed and used from the command line:
```shell
pip install conventional-pre-commit
```
Then run the command line script:
```shell
conventional-pre-commit [types] input
```
- `[types]` is an optional list of Conventional Commit types to allow (e.g. `feat fix chore`)
- `input` is a file containing the commit message to check:
```shell
conventional-pre-commit feat fix chore ci test .git/COMMIT_MSG
```
Or from a Python program:
```python
from conventional_pre_commit.format import is_conventional
# prints True
print(is_conventional("feat: this is a conventional commit"))
# prints False
print(is_conventional("nope: this is not a conventional commit"))
# prints True
print(is_conventional("custom: this is a conventional commit", types=["custom"]))
```
## Passing `args`
`conventional-pre-commit` supports a number of arguments to configure behavior:
```shell
$ conventional-pre-commit -h
usage: conventional-pre-commit [-h] [--force-scope] [--strict] [types ...] input
Check a git commit message for Conventional Commits formatting.
positional arguments:
types Optional list of types to support
input A file containing a git commit message
options:
-h, --help show this help message and exit
--force-scope Force commit to have scope defined.
--strict Force commit to strictly follow Conventional Commits formatting. Disallows fixup! style commits.
```
Supply arguments on the command-line, or via the pre-commit `hooks.args` property:
```yaml
repos:
- repo: https://github.com/compilerla/conventional-pre-commit
rev: <git sha or tag>
hooks:
- id: conventional-pre-commit
stages: [commit-msg]
args: [--strict, --force-scope, feat, fix, chore, test, custom]
```
**NOTE:** when using as a pre-commit hook, `input` is supplied automatically (with the current commit's message).
## Development
`conventional-pre-commit` comes with a [VS Code devcontainer](https://code.visualstudio.com/learn/develop-cloud/containers)
configuration to provide a consistent development environment.
With the `Remote - Containers` extension enabled, open the folder containing this repository inside Visual Studio Code.
You should receive a prompt in the Visual Studio Code window; click `Reopen in Container` to run the development environment
inside the devcontainer.
If you do not receive a prompt, or when you feel like starting from a fresh environment:
1. `Ctrl/Cmd+Shift+P` to bring up the command palette in Visual Studio Code
1. Type `Remote-Containers` to filter the commands
1. Select `Rebuild and Reopen in Container` to completely rebuild the devcontainer
1. Select `Reopen in Container` to reopen the most recent devcontainer build
## Versioning
Versioning generally follows [Semantic Versioning](https://semver.org/).
## Making a release
Releases to PyPI and GitHub are triggered by pushing a tag.
1. Ensure all changes for the release are present in the `main` branch
1. Tag with the new version: `git tag vX.Y.Z` for regular release, `git tag vX.Y.Z-preN` for pre-release
1. Push the new version tag: `git push origin vX.Y.Z`
## License
[Apache 2.0](LICENSE)
Inspired by matthorgan's [`pre-commit-conventional-commits`](https://github.com/matthorgan/pre-commit-conventional-commits).
Raw data
{
"_id": null,
"home_page": null,
"name": "conventional-pre-commit",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "git, pre-commit, conventional-commits",
"author": null,
"author_email": "Compiler LLC <dev@compiler.la>",
"download_url": "https://files.pythonhosted.org/packages/71/ca/2e2e0aca041306dd22d5adad87b5053f7e1c95a291f0148f0825f9c8ecd3/conventional_pre_commit-3.2.0.tar.gz",
"platform": null,
"description": "# conventional-pre-commit\n\nA [`pre-commit`](https://pre-commit.com) hook to check commit messages for\n[Conventional Commits](https://conventionalcommits.org) formatting.\n\nWorks with Python >= 3.8.\n\n## Usage\n\nMake sure `pre-commit` is [installed](https://pre-commit.com#install).\n\nCreate a blank configuration file at the root of your repo, if needed:\n\n```console\ntouch .pre-commit-config.yaml\n```\n\nAdd a new repo entry to your configuration file:\n\n```yaml\nrepos:\n # - repo: ...\n\n - repo: https://github.com/compilerla/conventional-pre-commit\n rev: <git sha or tag>\n hooks:\n - id: conventional-pre-commit\n stages: [commit-msg]\n args: []\n```\n\nInstall the `pre-commit` script:\n\n```console\npre-commit install --hook-type commit-msg\n```\n\nMake a (normal) commit :x::\n\n```console\n$ git commit -m \"add a new feature\"\n\n[INFO] Initializing environment for ....\nConventional Commit......................................................Failed\n- hook id: conventional-pre-commit\n- duration: 0.07s\n- exit code: 1\n\n[Bad Commit message] >> add a new feature\n\nYour commit message does not follow Conventional Commits formatting\nhttps://www.conventionalcommits.org/\n\nConventional Commits start with one of the below types, followed by a colon,\nfollowed by the commit message:\n\n build chore ci docs feat fix perf refactor revert style test\n\nExample commit message adding a feature:\n\n feat: implement new API\n\nExample commit message fixing an issue:\n\n fix: remove infinite loop\n\nExample commit with scope in parentheses after the type for more context:\n\n fix(account): remove infinite loop\n\nExample commit with a body:\n\n fix: remove infinite loop\n\n Additional information on the issue caused by the infinite loop\n```\n\nMake a (conventional) commit :heavy_check_mark::\n\n```console\n$ git commit -m \"feat: add a new feature\"\n\n[INFO] Initializing environment for ....\nConventional Commit......................................................Passed\n- hook id: conventional-pre-commit\n- duration: 0.05s\n```\n\n## Install with pip\n\n`conventional-pre-commit` can also be installed and used from the command line:\n\n```shell\npip install conventional-pre-commit\n```\n\nThen run the command line script:\n\n```shell\nconventional-pre-commit [types] input\n```\n\n- `[types]` is an optional list of Conventional Commit types to allow (e.g. `feat fix chore`)\n\n- `input` is a file containing the commit message to check:\n\n```shell\nconventional-pre-commit feat fix chore ci test .git/COMMIT_MSG\n```\n\nOr from a Python program:\n\n```python\nfrom conventional_pre_commit.format import is_conventional\n\n# prints True\nprint(is_conventional(\"feat: this is a conventional commit\"))\n\n# prints False\nprint(is_conventional(\"nope: this is not a conventional commit\"))\n\n# prints True\nprint(is_conventional(\"custom: this is a conventional commit\", types=[\"custom\"]))\n```\n\n## Passing `args`\n\n`conventional-pre-commit` supports a number of arguments to configure behavior:\n\n```shell\n$ conventional-pre-commit -h\nusage: conventional-pre-commit [-h] [--force-scope] [--strict] [types ...] input\n\nCheck a git commit message for Conventional Commits formatting.\n\npositional arguments:\n types Optional list of types to support\n input A file containing a git commit message\n\noptions:\n -h, --help show this help message and exit\n --force-scope Force commit to have scope defined.\n --strict Force commit to strictly follow Conventional Commits formatting. Disallows fixup! style commits.\n```\n\nSupply arguments on the command-line, or via the pre-commit `hooks.args` property:\n\n```yaml\nrepos:\n - repo: https://github.com/compilerla/conventional-pre-commit\n rev: <git sha or tag>\n hooks:\n - id: conventional-pre-commit\n stages: [commit-msg]\n args: [--strict, --force-scope, feat, fix, chore, test, custom]\n```\n\n**NOTE:** when using as a pre-commit hook, `input` is supplied automatically (with the current commit's message).\n\n## Development\n\n`conventional-pre-commit` comes with a [VS Code devcontainer](https://code.visualstudio.com/learn/develop-cloud/containers)\nconfiguration to provide a consistent development environment.\n\nWith the `Remote - Containers` extension enabled, open the folder containing this repository inside Visual Studio Code.\n\nYou should receive a prompt in the Visual Studio Code window; click `Reopen in Container` to run the development environment\ninside the devcontainer.\n\nIf you do not receive a prompt, or when you feel like starting from a fresh environment:\n\n1. `Ctrl/Cmd+Shift+P` to bring up the command palette in Visual Studio Code\n1. Type `Remote-Containers` to filter the commands\n1. Select `Rebuild and Reopen in Container` to completely rebuild the devcontainer\n1. Select `Reopen in Container` to reopen the most recent devcontainer build\n\n## Versioning\n\nVersioning generally follows [Semantic Versioning](https://semver.org/).\n\n## Making a release\n\nReleases to PyPI and GitHub are triggered by pushing a tag.\n\n1. Ensure all changes for the release are present in the `main` branch\n1. Tag with the new version: `git tag vX.Y.Z` for regular release, `git tag vX.Y.Z-preN` for pre-release\n1. Push the new version tag: `git push origin vX.Y.Z`\n\n## License\n\n[Apache 2.0](LICENSE)\n\nInspired by matthorgan's [`pre-commit-conventional-commits`](https://github.com/matthorgan/pre-commit-conventional-commits).\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
"summary": "A pre-commit hook that checks commit messages for Conventional Commits formatting.",
"version": "3.2.0",
"project_urls": {
"code": "https://github.com/compilerla/conventional-pre-commit",
"tracker": "https://github.com/compilerla/conventional-pre-commit/issues"
},
"split_keywords": [
"git",
" pre-commit",
" conventional-commits"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "dcb76519ee990c92cce7cb192e83e0382eeb2ccfa8a472818ab7b5feea95e138",
"md5": "16303cac00a3e44d5c5b2e2064d6f430",
"sha256": "765ff6abed9a1d9866037d3007f154793ef851547da04ef0b6da26a1ef242e6e"
},
"downloads": -1,
"filename": "conventional_pre_commit-3.2.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "16303cac00a3e44d5c5b2e2064d6f430",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 14545,
"upload_time": "2024-03-29T17:40:11",
"upload_time_iso_8601": "2024-03-29T17:40:11.363180Z",
"url": "https://files.pythonhosted.org/packages/dc/b7/6519ee990c92cce7cb192e83e0382eeb2ccfa8a472818ab7b5feea95e138/conventional_pre_commit-3.2.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "71ca2e2e0aca041306dd22d5adad87b5053f7e1c95a291f0148f0825f9c8ecd3",
"md5": "288599f7429fffa06edf685ee820b772",
"sha256": "08369374ff458faec7ed0caa2b0f4f76c0800b49c513f6f0641e9258d0cf9775"
},
"downloads": -1,
"filename": "conventional_pre_commit-3.2.0.tar.gz",
"has_sig": false,
"md5_digest": "288599f7429fffa06edf685ee820b772",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 22421,
"upload_time": "2024-03-29T17:40:12",
"upload_time_iso_8601": "2024-03-29T17:40:12.508859Z",
"url": "https://files.pythonhosted.org/packages/71/ca/2e2e0aca041306dd22d5adad87b5053f7e1c95a291f0148f0825f9c8ecd3/conventional_pre_commit-3.2.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-29 17:40:12",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "compilerla",
"github_project": "conventional-pre-commit",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "conventional-pre-commit"
}
