Workflow run from comment to get format auto commit.

[Tatsinnit]

This is for the case where users who are maintainers will be able to run the prettier write against a repo by simply calling this /format from the comment and it will auto add the commit for the format.

This is phase-1 in the second phase - we will add the husky pre-commit formatter as well, that will require some setting form the user but we can always hook for the repo as a script command run from the machine like npm run setup-husky-pre-commit-check

Please don't worry about the current prettier issue it's because we surpassed one rule which I've enabled it again. = )

• Sample run here: Update index.ts Tatsinnit/setup-kubectl#7
• Sample workflow which adds the commit: https://github.com/Tatsinnit/setup-kubectl/actions/runs/15842557323/job/44657786483

Thanks

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow to automatically run Prettier formatting on a PR when a maintainer comments /format, and updates the Prettier dependency to allow minor/patch bumps.

• Switches prettier dependency in package.json to a caret range
• Introduces .github/workflows/format-from-comment.yml to trigger and commit formatting via an issue comment

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
package.json	Changed Prettier from an exact version to a caret range
.github/workflows/format-from-comment.yml	New workflow to run npm run format and auto-commit changes

Comments suppressed due to low confidence (2)

.github/workflows/format-from-comment.yml:20

• Pinning to a commit SHA prevents automatic patch updates; consider using a version tag like actions/checkout@v3 for maintainability.

        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683

.github/workflows/format-from-comment.yml:27

• Pinning to a commit SHA here also locks you out of receiving fixes; using actions/setup-node@v3 ensures you get updates without unexpected major changes.

        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020

[davidgamero]

based on the that test workflow run it looks like the commits are not signed?

[bosesuneha]

why not add a pre-commit hook directly?

[Tatsinnit]

based on the that test workflow run it looks like the commits are not signed?

Yeah that I did noticed :) latter in night, hence I park this PR for ease and FYI - the only advantage for this comment hook could be when everyone are in fly and we need something quick to fix for prettier. (aka folks away from machine)

[Tatsinnit]

why not add a pre-commit hook directly?

Ah you mean host machine hook or directly at repo level, for repo level it might need some sort of setting with shell, yeah let me play around more.

[bosesuneha]

why not add a pre-commit hook directly?

Ah you mean host machine hook or directly at repo level, for repo level it might need some sort of setting with shell, yeah let me play around more.

I meant having a pre-commit hook in the repo

[Tatsinnit]

why not add a pre-commit hook directly?

Ah you mean host machine hook or directly at repo level, for repo level it might need some sort of setting with shell, yeah let me play around more.

I meant having a pre-commit hook in the repo

#171 I guess fits what you jsut said and it does make sense, thank you = )

[Tatsinnit]

Closing in favour of #171 , thanks!