Is your feature request related to a problem?
There are more configurable options for yamlfmt than the subset on this GitHub Action.
What solutions have you considered?
In the event that an existing config file is already in place, it would be good if this Action could make use of that.
Some logic could also be added to merge the pre-existing config file with the Action inputs, rather than the Action generating its own config file and using only that.
What alternatives have you considered?
The way that the logic in this Action is wired up, the interface doesn't really leave anything to chance. It only works with input values and choices that are explicitly defined in the action.yml file, which leaves out other configurable options that yamlfmt has support for.
Additional context
No response
Code of Conduct
Is your feature request related to a problem?
There are more configurable options for
yamlfmtthan the subset on this GitHub Action.What solutions have you considered?
In the event that an existing config file is already in place, it would be good if this Action could make use of that.
Some logic could also be added to merge the pre-existing config file with the Action inputs, rather than the Action generating its own config file and using only that.
What alternatives have you considered?
The way that the logic in this Action is wired up, the interface doesn't really leave anything to chance. It only works with input values and choices that are explicitly defined in the
action.ymlfile, which leaves out other configurable options thatyamlfmthas support for.Additional context
No response
Code of Conduct