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

Improve changelog generation #381

Closed
schurzi opened this issue Jan 22, 2021 · 4 comments
Closed

Improve changelog generation #381

schurzi opened this issue Jan 22, 2021 · 4 comments

Comments

@schurzi
Copy link
Contributor

schurzi commented Jan 22, 2021

Is your feature request related to a problem? Please describe.
We are using github_changelog_generator to generate our changelogs. The tool can include labels, but this feature is currently broken. So we had to disable this feature.

Describe the solution you'd like
We want a changelog, which includes a label for each Issue/PR that is listet. The label is used to highlight which role (os_hardening, ssh_hardening, nginx_hardening, mysql_hardening) was affected by the issue/PR.

example current:


  • Default value for ssh_max_startups should be changed #366

example wanted:



Describe alternatives you've considered
Currently I see two options:

  • wait till the fix for github_changelog_generator is released
  • use a different changelog generator

Additional context
Our current changelog generator has options to include labels, but this is broken. We are using version 0.15.2 (https://github.com/charmixer/auto-changelog-action/blob/master/Dockerfile) which misses the fix (github-changelog-generator/github-changelog-generator@8525969).

@rndmh3ro
Copy link
Member

We could also fork both projects and update the Dockerfile and action ourselves.

@joubbi
Copy link
Contributor

joubbi commented Feb 2, 2021

Is this issue blocking you from creating a new release? It would help me if you made a new release of the collection with all the commits since November 11 2020.

@schurzi
Copy link
Contributor Author

schurzi commented Feb 2, 2021

@joubbi no this is not blocking. But we had some other problems with the release workflow. They are now fixed an I scheduled a release.

@rndmh3ro
Copy link
Member

closed by #446

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants