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

Changelog Generation as Artifact of Pipeline Execution #391

Open
pmsmm opened this issue Jun 4, 2024 · 0 comments
Open

Changelog Generation as Artifact of Pipeline Execution #391

pmsmm opened this issue Jun 4, 2024 · 0 comments

Comments

@pmsmm
Copy link

pmsmm commented Jun 4, 2024

Hello everyone and apologies if this issue is a consequence of me not finding the proper documentation but I've searched quite a lot.

Basically I'm in the process of generating a CHANGELOG.md file so that I can send that file off to someone else. I've read in the FAQ that commiting a changelog to the repository introduces some complexities that should be avoided when possible.

Given this I've been attempting, so far to no success, to generate the changelog and save it as an artifact of my pipeline so that I can then manually retrieve it and send it to the desired person.

Is this something that can actually be done with the changelog plugin or is the only way of achieving this through commiting the changelog file to the repository? If this is actually possible then my suggestion would be to add an example to the documentation just as a heads up to people that want to avoid the added complexity of commiting these files back onto the repository.

Just a heads up, our current workflow implies copying the release notes generated during dry-run and then sending them off somewhere, what we intend to achieve is to just get a simple file (CHANGELOG.md) and send it to someone.

Thanks in advance

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

1 participant