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
Allow inputing config-name file contents #1338
Comments
An example repo that has several drafter files that could be created during the workflow so if a new service gets added, you don't have to worry about the config files: |
+1 to this. Currently any release drafter config - even one supplied to the action through My use case is similar to as described in #336 (comment) - I want to set |
If my workflow requires multiple release-drafter configs that are dependent on the contents of the repo, I want to dynamically supply those as a
config-name
parameter. This will help not having to create/delete files in the.github
directory as new configs are necessary. It would nice to input the config file as text or be able to write the config during the workflow run.The text was updated successfully, but these errors were encountered: