feat(action): add github action for cargo.toml formating

[gwen-lg]

Note: this is a first version for comments

It's great to have Cargo.toml (by example) formatted on save in VSCode. But If it's not checked in CI, this is dependent of developer use Even Better TOML and process.

TODO:

• manage config with indent_string=" " for Cargo.toml (like Even Better TOML)
• convert output to display beautiful error/warning in github
• feature for allow automatic patch commits ?

#470

Work inspired from https://github.com/marketplace/actions/typos-action

[panekj]

Taplo is already usable in GHA via uses: docker://tamasfe/taplo

[JounQin]

Why not https://autofix.ci?

[panekj]

Why not autofix.ci?

Maybe someone doesn't want to pay for it?

[JounQin]

Maybe someone doesn't want to pay for it?

Hah, isn't it free?

[panekj]

Maybe someone doesn't want to pay for it?

Hah, isn't it free?

Not for private repos

[JounQin]

Not for private repos

How is it related to private repos here?

[panekj]

You brought up autofix.ci?

[JounQin]

You brought up autofix.ci?

But taplo is not a private repo?

[panekj]

And the PR isn't about using taplo for taplo repository. You're suggesting using autofix.ci for something, I don't know what. The PR adds GitHub actions for uing taplo in GHA which can be used in public repos, private repos, GHES, whatever.

[JounQin]

And the PR isn't about using taplo for taplo repository. You're suggesting using autofix.ci for something, I don't know what. The PR adds GitHub actions for uing taplo in GHA which can be used in public repos, private repos, GHES, whatever.

Sorry I misunderstood what this PR does. :(

[gwen-lg]

Taplo is already usable in GHA via uses: docker://tamasfe/taplo

Do you prefer a GitHub Action based on docker image, instead of release files ?

I found no documentation about how to use taplo in GitHub Workflow. So a dedicated GitHub Action might be helpful to users.

[tobiasdiez]

Docker-based actions are not available for macos and windows (based on https://docs.github.com/en/actions/sharing-automations/creating-actions/about-custom-actions#types-of-actions)

[panekj]

If it's going to be action then it should just run taplo, adding commands checking and file arguments is super awkward when the configuration is supposed to live in /taplo.toml (or /.taplo.toml)

- uses: taplo
  with:
    format: true/false
    lint: true/false

[panekj]

Although I think I'd prefer it to be in NodeJS and not shell

[gwen-lg]

If it's going to be action then it should just run taplo, adding commands checking and file arguments is super awkward when the configuration is supposed to live in /taplo.toml (or /.taplo.toml)

- uses: taplo
  with:
    format: true/false
    lint: true/false

I'm ok with this, I can update action in this direction.

Although I think I'd prefer it to be in NodeJS and not shell

I am not against it, but I haven't the knowledge to do this. So unless it's really simple and has examples to guide me, someone else will have to do it.

[gwen-lg]

@panekj : I have updated with simpler version. I have keep the setup of version, and format_write_changes this second can also be removed if it's preferred. I have add a small part for doc in README.md, I haven't take time to create a page in website documentation, perhaps it's better/or complementary to README.md.