vouch

Looks like https://github.com/suzuki-shunsuke/pinact/pull/1558 is giving us issues on our Vouch action in Ghostty: According to the aforementioned issue, it looks like we're going to have to start tagging versions to ensure they pass pinact. There was a proposal to add branch comments, but it looks like it was ultimately closed as not planned for the time being. This probably means we'll need to tag new changes going forward too when we want to bump vouch in Ghostty. PS: Looks like we could add an ignore rule, but I'd imagine getting into the habit of doing this would not be in the right spirit of checking pins in the first place. 🙂

It would be nice to have an input to override the commit message used by , so the generated commit can follow a project's commit conventions (e.g. Conventional Commits). example: I tried a workaround using and calling the vouch command directly, but ran into an escaping bug in the wrapper that prevents passing a multi-word commit message: #94

The wrapper installed by cannot pass arguments that contain spaces (or other special chars) to nushell. Any multi-word argument is broken before it reaches the nushell command. I tried to workaround the action to add a custom commit message, but got an error. To reproduce this issue, you can find my test workflow here: https://github.com/meteyou/vouch-system-test/blob/2ad01e7a72b6723ce8e258c2009a0d6a85e68a03/.github/workflows/vouch-manage-by-issue.yml#L25-L40 and here you can find the failed run: https://github.com/meteyou/vouch-system-test/actions/runs/28329531587/job/83925189414