semvec/pypi-packages huggingface dataset:
gitlab-changelog-gen 0.0.3
A command line utility to generate CHANGELOG.md with Gitlab merge requests
License: MIT
Keywords: gitlab changelog python

# Gitlab Changelog Generator

A command line utility to generate CHANGELOG.md for a gitlab repository.

The merged merge requests tagged with a milestone will be collected to generate the changelog.

## Install

```bash
# pip install gitlab-changelog-gen
```

## Usage

```shell
# chg-gen init
Gitlab host: https://your-gitlab.com
Gitlab group: your-group
Gitlab project: your-project
Gitlab private token: your-token
# chg-gen output
Changelog is generated to './CHANGELOG.md' success.
```

## Configuration

Before generate the changelog file, you need to run `chg-gen init` to init the config first. The default config file
is `.chg-gen.config` under the working directory.

The config file is `YAML` format, and this is the instructions:
```yaml
// host address of your gitlab
host: https://gitlab.example
// group name of your repo
group: foo
// project name of your repo
project: bar
// private_token to access your gitlab API
private_token: yourtoken
```

## Generation Rules

The generation rules of a changelog consist of:

* Release: A `release` section contains `features` and `bug fixes`. The release name is the title of `milestone`
of the project.
* Features: Composed by the merged `merge requests` labeled with `feature` or `enhancement`.
* Bug Fixes: Composed by the merged `merge requests` labeled with `bug`.
* Change Items: Components of `Features` and `Bug Fixes`. The content is the title of the `merge request` with its
reference and the `author` reference.

An example of [CHANGELOG.md](https://github.com/tossmilestone/gitlab-changelog-gen/blob/master/example/CHANGELOG.md).
shhh 0.1.0
Structured HTTP Headers (handily)
License: MIT
Requires Python: >=3.5

# Shhh!

## Structured HTTP Headers (handily)

This is a [Python 3](https://python.org/) library implementing parsing and serialisation of [Structured Headers for HTTP](https://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html).

Shhh's initial purpose is to prove the algorithms in the specification; as a result, it is not at all optimised. It tracks the specification closely, but since it is not yet an RFC, may change at any time.

The top-level `parse` and `serialise` functions are the ones your code should call.