Skip to content

Github Action for creating a CHANGELOG.md file based on semver and conventional commits.

License

Notifications You must be signed in to change notification settings

nuuday/github-changelog-action

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Generate changelog with git-chglog

Github Action for creating a CHANGELOG.md file based on semver and conventional commits.

Usage

Pre-requisites

Create a workflow .yml file in your repositories .github/workflows directory. An example workflow is available below. For more information, reference the GitHub Help Documentation for Creating a workflow file.

Further more you need to have git-chlog configured and have the configuration added to your git repository.

Inputs

  • next_version: Next version number
  • config_dir: git-chglog configuration directory. Default: .ghglog
  • filename: Filename to write the changelog to. Default: CHANGELOG.md
  • tag: Optional, Generate changelog only for this tag.

Outputs

  • changelog: Changelog content if no filename input is empty

Example workflow - upload a release asset

On every push to master generate a CHANGELOG.md file.

name: Build and release
on: 
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

jobs:
  package:
    runs-on: ubuntu-latest
    steps:
      - uses: nuuday/github-changelog-action@v1.0.0
        with:
          next_version: "1.0.0"      

License

The scripts and documentation in this project are released under the MIT License

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

  • Steffen F. Qvistgaard - Initial work - ssoerensen

See also the list of contributors who participated in this project.