RoryDoherty

Should the docs be updated around `ty` and `stdin` to say that these options will not actually work then?

Also seeing this issue: ``` npm: '8.19.4' node: '16.20.2' ``` OS is ubuntu ``` npm view xunit-viewer version 10.5.1 ``` ``` xunit-viewer --version unknown ```

Also running into this on version v3.4.3, could we remove the stale label I'd also like to be able to template out the `command` field as well

> This seems like a bug. Would anyone like to submit a PR to fix it? @terrytangyuan I have opened a PR with a fix for this https://github.com/argoproj/argo-workflows/pull/10784

I also think the settings in config could be used to implement this: https://github.com/palantir/policy-bot/issues/387 Could have another option called approve_pr_on_success_status

@bluekeyes thanks for the feedback, I've updated this PR so that it is just the option to not set failure status checks and opened this PR https://github.com/palantir/policy-bot/pull/712 with the changes...

@bluekeyes would you be able to take a look at this PR anytime soon? I'm eager to also implement https://github.com/palantir/policy-bot/issues/387 as these missing features are blocking us from currently rolling...

Unfortunately the changes you've suggested would make this feature unusable for us 1. If a matching policy fails I just want it to be ignored completely, I wouldn't want to...

FYI these are the Critical CVEs detected by [trivy](https://github.com/aquasecurity/trivy) in the latest release 0.10.17 ``` CVE-2019-8457 CVE-2021-29921 CVE-2021-41945 CVE-2023-23914 CVE-2023-28322 ```

Just wondering if this was ever implemented or is it still on the backlog?