Allow inputing config-name file contents

[ksolie]

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.

[ksolie]

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:
https://github.com/guardrail-dev/guardrail/tree/master/.github

[mrfelton]

+1 to this. Currently any release drafter config - even one supplied to the action through config-name property - needs to exist on the default branch in order to be usable. That prevents the possibility of creating the release drafter config dynamically at run time.

My use case is similar to as described in #336 (comment) - I want to set include-paths dynamically at run time. Currently this doesn't seem possible since I can't create a dynamic release drafter config and I can't override include-paths on the action config.