Metadata-Version: 2.4
Name: changelet
Version: 0.4.0
Summary: Not getting merged 
Home-page: https://github.com/octodns/changelet
Author: Ross McFarland
Author-email: rwmcfa1@gmail.com
License: MIT
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: PyYaml
Requires-Dist: semver>=3.0.0
Provides-Extra: dev
Requires-Dist: pytest; extra == "dev"
Requires-Dist: pytest-cov; extra == "dev"
Requires-Dist: pytest-network; extra == "dev"
Requires-Dist: black<25.0.0,>=24.3.0; extra == "dev"
Requires-Dist: build>=0.7.0; extra == "dev"
Requires-Dist: isort>=5.11.5; extra == "dev"
Requires-Dist: pyflakes>=2.2.0; extra == "dev"
Requires-Dist: readme_renderer[md]>=26.0; extra == "dev"
Requires-Dist: twine>=3.4.2; extra == "dev"
Provides-Extra: test
Requires-Dist: pytest; extra == "test"
Requires-Dist: pytest-cov; extra == "test"
Requires-Dist: pytest-network; extra == "test"
Dynamic: author
Dynamic: author-email
Dynamic: description
Dynamic: description-content-type
Dynamic: home-page
Dynamic: license
Dynamic: license-file
Dynamic: provides-extra
Dynamic: requires-dist
Dynamic: requires-python
Dynamic: summary

Not getting merged 

## ChangeLog and Release Management Tooling

A simple standalone Python module for CHANGELOG and release management. Spun out of [octoDNS](https://github.com/octodns/octodns/).

### Installation

#### Command line

```console
pip install changelet
```

### Usage

For help with using the command

```console
changelet --help
```

In most cases the only command you're likely to encounter is `create`. It will be used to add a changelog entry to your branch/PR.

```console
changelet create --type (TYPE) Short description of your change to be included in the changelog
```

The options for type are
* `major` - rare for non-maintainers, a change that will break backwards compatibility and require users to take care when updating
* `minor` - adds new functionality that is either self contained or done in a completely backwards compatible manner
* `patch` - fixes an issue or bug with existing functionality
* `none` - change that should not be included in the CHANGELOG and will not directly impact users, e.g. documentation, README, tooling, ...

#### Slash Command

There is an optional GitHub slash command action that can installed. If it's installed users with write permissions to the repo can add a comment in the PR to add Changelog entries. The interface is almost idential to the command line, though only the create command is supported at this time.

```console
/changelog create -t none This is an example changelog entry added as a PR comment
```

### Using changlet

Currently the tooling has only been tested with repositories in the octoDNS org, but it should be usable elsewhere. You'll want to have a look at the following for how to incorporate it into your repo and workflows.

* [(octodns) script/changelog](https://github.com/octodns/octodns/blob/main/script/changelog)
* [.git_hooks_pre-commit](.git_hooks_pre-commit) (and [script/bootstrap](script/bootstrap) which installs it)
* [.github/workflows/changelog.yml](.github/workflows/changelog.yml)

### Development

See the [/script/](/script/) directory for some tools to help with the development process. They generally follow the [Script to rule them all](https://github.com/github/scripts-to-rule-them-all) pattern. Most useful is `./script/bootstrap` which will create a venv and install both the runtime and development related requirements. It will also hook up a pre-commit hook that covers most of what's run by CI.
