@pascaljoly I've also investigated the gitleaks license key issue and it seems that a limitation of the gitleaks secret scanning is that it doesn't work on community fork contributions like yours per this github issue: gitleaks/gitleaks#2063
You can see new PR's I opened from inside the repo run fine, like this one, which means the API key is working: #21
I'll try to investigate a workaround but for now, let's just ignore that failing check.
Originally posted by @keenanjohnson in #20 (comment)
@pascaljoly I've also investigated the gitleaks license key issue and it seems that a limitation of the gitleaks secret scanning is that it doesn't work on community fork contributions like yours per this github issue: gitleaks/gitleaks#2063
You can see new PR's I opened from inside the repo run fine, like this one, which means the API key is working: #21
I'll try to investigate a workaround but for now, let's just ignore that failing check.
Originally posted by @keenanjohnson in #20 (comment)