Related GitHub Issues

Problem

Test mode PR comments are awesome, but it would be even more awesome if users could customize what the PR comment content is.

Solution

Users can provide their own string template. Then, we provide an object with a bunch of variables in it, and we can use that to render the comment.

To users who do not use this feature, this feature will feel like a refactor to them where they will continue to see the default PR comment being used.

Testing

• Added automated tests.
• Manually tested. If you check this box, provide instructions for others to test, too.

Pushed some testing commits to this PR to make sure that it works as expected.

Notes for reviewers

The original error message I got when running the code in the CI was talking about regex, which is super confusing when I wasn't passing regex at all.

So, I just think we need to have a better error message in general to help if users encounter a problem.
- test that we can still use default pull request comment template
- fix: escape the pull request template string

When you pass in the template string as a param, there's a good chance that it uses different kinds of quotes inside of it, which then messes with the CLI Bash command that we're running, where we're trying to pass the string into decaf. So, as a way to properly escape that string you pass in, we write to a temporary file and then just pass that file to decaf.
- test if you can pass a template or pr comments
- improve the README pull request comment sample by using a loop
- completely replace contents of PR comment each time, dont append

Because we're using string templates now, we don't want to use the appending feature of appending context to the existing PR comment. We want to completely replace it instead, just because then you don't have to add a bunch of logic to your string template.
- refactor: document usage of ventojs for later reference

to help devs + agents learn ventojs quickly, putting documentation in the code via comments with basic usage.
- feat: customize pull request comment by providing a template string
- add inputs for providing a pull request comment template string. either file or string.
- refactor: replace jsr:deno-library/template with npm:ventojs for string template engine

deno-library/template doesn't offer support for loops and I'll be needing that allowing users to provide a custom PR comment.

I chose vento because...

• very similar syntax to deno-library/template (using {{...}}) to be simple and easy to use.
• gives more powerful features like loops, conditionals.
• zero dependencies. small. simple.