-
Notifications
You must be signed in to change notification settings - Fork 8
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
Introduce a Dockerized version of the tool + Add support of generating YAML files as an output #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be on the right way. Some implementation feedback.
end | ||
puts changelog_yaml | ||
|
||
changelog_path = ENV["CHANGELOG_YAML_PATH"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency with the previous behavior would be preferable as an optional additional argument.
Alternatively, and this seems preferable, shouldn't this be the job of the invoker, i.e. docker-runner.rb
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then you would need to parse the CLI output there which is not fun.
Regarding optional arguments, it requires adding a CLI arguments framework to do it well. I could do it, but IMHO it is a separate story since the tool already uses environment variables in the script. Subject for further improvement
changelog_yaml = backported_issues.to_yaml | ||
puts changelog_yaml | ||
|
||
changelog_path = ENV["CHANGELOG_YAML_PATH"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, seems to make more sense as an argument.
Co-Authored-By: Daniel Beck <1831569+daniel-beck@users.noreply.github.com>
@daniel-beck @MarkEWaite ready for final review IMHO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It worked for me when I used the instructions in the README to run a Docker image that I created from the Dockerfile in this pull request
i will merge it to setup a CD Pipeline for the tool |
@daniel-beck @MarkEWaite . I am experimenting with a Dockerized version of the tool for automated changelog generation with a GitHub Actions PoC. This PR kinda works, but it is in progress for now