Metadata-Version: 2.1
Name: pyinvc
Version: 0.1.31
Summary: 
Author: Alireza
Author-email: arg274@gmail.com
Requires-Python: >=3.12,<4.0
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Requires-Dist: httpx (>=0.28.1,<0.29.0)
Requires-Dist: python-decouple (>=3.8,<4.0)
Description-Content-Type: text/markdown

# pyinvc
Baloot billing module

# Contributing to the Project

## Commit Messages

We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). The commit message should be structured as follows:

```
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

Here's a list of `types` you can use for your commit message:

- **feat**: A new feature
- **fix**: A bug fix
- **docs**: Documentation changes
- **style**: Code style changes (like formatting)
- **refactor**: Code changes that neither fix a bug nor add a feature
- **test**: Adding or modifying tests
- **chore**: Routine tasks, such as dependencies updates

Commit message example:
```
feat(auth): add login API endpoint
feat(lang): add Polish language
```
