Code Monkey home page Code Monkey logo

changelogging's Introduction

Image

changelogging

License Version PyPI Version Downloads PyPI Downloads Discord Test

Building changelogs from fragments.

Installation

The binaries can be downloaded from releases.

pipx

Note: because changelogging was originally written in python, releases on PyPI have different versions: for instance, the 0.4.1 release is on PyPI with version 2.4.1, meaning the major part of the version is always incremented twice to get the PyPI one.

Installing changelogging with pipx is quite simple:

$ pipx install changelogging

Alternatively, the package can be installed from source:

$ pipx install git+https://github.com/nekitdev/changelogging.git

Or via cloning the repository:

$ git clone https://github.com/nekitdev/changelogging.git
$ cd changelogging
$ pipx install .

cargo

Installing the crate with cargo is as simple as with pipx:

$ cargo install changelogging

Alternatively, the crate can be installed from source:

$ cargo install --git https://github.com/nekitdev/changelogging.git

Or via cloning the repository:

$ git clone https://github.com/nekitdev/changelogging.git
$ cd changelogging
$ cargo install --path .

Example

Once changelogging is installed, we can start building changelogs!

First things first, we need to configure the context of the project.

Create changelogging.toml and add the name, version and URL of the project:

[context]
name = "changelogging"
version = "0.4.1"
url = "https://github.com/nekitdev/changelogging"

Then we need to create the changes directory.

$ mkdir changes

Now we can add fragments:

$ changelogging create --content "Added cool features!" 13.feature.md
$ changelogging create --content "Fixed annoying bugs!" 64.fix.md

And finally, preview the changelog entry!

$ changelogging preview
## 0.4.1 (YYYY-MM-DD)

### Features

- Added cool features! (#13)

### Fixes

- Fixed annoying bugs! (#64)

Then let us add our CHANGELOG.md file with the following content:

# Changelog

<!-- changelogging: start -->

Note that the start is essential if we want to add some content before the changelog entries.

Assuming the preview is what we expected it to be, writing it to the changelog is as simple as:

$ changelogging build

Finally, let's see the changelog:

$ cat CHANGELOG.md
# Changelog

<!-- changelogging: start -->

## 0.4.1 (YYYY-MM-DD)

### Features

- Added cool features! (#13)

### Fixes

- Fixed annoying bugs! (#64)

Documentation

You can find the documentation here.

Support

If you need support with the library, you can send an email or refer to the official Discord server.

Changelog

You can find the changelog here.

Security Policy

You can find the Security Policy of changelogging here.

Contributing

If you are interested in contributing to changelogging, make sure to take a look at the Contributing Guide, as well as the Code of Conduct.

License

changelogging is licensed under the MIT License terms. See License for details.

changelogging's People

Contributors

dependabot[bot] avatar nekitbot avatar nekitdev avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

changelogging's Issues

Add git functionality.

This issue proposes to add git functionality for:

  • adding changelog fragments after changelogging create;
  • staging the changelog after changelogging build;
  • removing the fragments.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.