On Fri, Feb 25, 2022 at 11:49 AM Daniel Beck <db...@cloudbees.com> wrote:
> > It looks like GitHub's action can do what I cannot because it uses an > undocumented API. > > > I'll update this thread once it works, meanwhile you can watch > https://github.com/jenkins-infra/jenkins-security-scan/issues/3 > I've updated the workflow to properly work with pull requests from forks. The result with the now used GH action to upload the scan result differs from the scan result upload API's, so I've decided to increase the version of the workflow to v2. v1 still works as before, but you need v2 for full PR support. https://github.com/jenkins-infra/jenkins-security-scan/releases/tag/v2 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLRqSqf6s-9ddmY00gzyhu8-iarZZtLrKPeTAtRip6Grw%40mail.gmail.com.
