Skip to content

Automating release notes from CI #984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jalvesz opened this issue Apr 22, 2025 · 1 comment
Open

Automating release notes from CI #984

jalvesz opened this issue Apr 22, 2025 · 1 comment
Labels
automation Related to the workflows and automatic tests running here documentation Improvements or additions to documentation help wanted Extra attention is needed idea Proposition of an idea and opening an issue to discuss it

Comments

@jalvesz
Copy link
Contributor

jalvesz commented Apr 22, 2025

Motivation

I've been looking at ways to ease the generation of releases. I found two options that seems interesting:

  1. https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
  2. https://git-cliff.org/ > https://git-cliff.org/docs/category/github-actions

I wanted to see if the use of any of these tools could help facilitate making more regular releases.

Any experience with these tools?

Prior Art

No response

Additional Information

No response

@jalvesz jalvesz added idea Proposition of an idea and opening an issue to discuss it documentation Improvements or additions to documentation help wanted Extra attention is needed automation Related to the workflows and automatic tests running here labels Apr 22, 2025
@stigh
Copy link
Contributor

stigh commented Apr 22, 2025

I think this is a great idea! To help keep the Git history clean and make changelog automation easier (especially with git-cliff), I’d suggest:

  1. Enabling squash-on-merge for the repo. This prevents intermediate commits from cluttering the history. It works best when PRs are kept small and focused.

  2. Adopting conventional commits (https://www.conventionalcommits.org/en/v1.0.0/), which git-cliff relies on for changelog generation. One approach is to use the conventional message as the PR title, since that becomes the final commit message after squashing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Related to the workflows and automatic tests running here documentation Improvements or additions to documentation help wanted Extra attention is needed idea Proposition of an idea and opening an issue to discuss it
Projects
None yet
Development

No branches or pull requests

2 participants