Skip to content
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

[BUG] GoReleaser Changelog does not consider groups #39

Closed
2 tasks done
ludelafo opened this issue Jun 8, 2024 · 0 comments · Fixed by #44
Closed
2 tasks done

[BUG] GoReleaser Changelog does not consider groups #39

ludelafo opened this issue Jun 8, 2024 · 0 comments · Fixed by #44
Labels
New New issue that has not been read yet

Comments

@ludelafo
Copy link
Owner

ludelafo commented Jun 8, 2024

Before you submit your issue, please review the following elements. Check the boxes below to confirm that you have read and understood each item.

  • I have read and agreed to panosse's Contributing guide.
  • I have checked that the issue does not already exist or has not already been resolved in another issue or pull request.

Describe the bug

panosse uses Pull Requests (from Issues) to improve panosse. As all commits in a pull request are squashed to keep a clean Git history, all pull requests keep the names [FEATURE] or [BUG] from their related issue.

As for now, GoReleaser does not seem to correctly pick up those commit messages to generate the groups in the releases page as described in the GoReleaser configuration file of this project.

More documentation in the official documentation at https://goreleaser.com/customization/changelog/.

To reproduce

  1. Create a new Git tag
  2. Workflow runs and create a new release
  3. The release does not contain the groups "Features" and Bug fixes"

Expected behavior

The changelog should contain the three categories "Features", "Bug fixes" and "Others".

@ludelafo ludelafo added the New New issue that has not been read yet label Jun 8, 2024
@ludelafo ludelafo linked a pull request Jun 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New New issue that has not been read yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant