Support nested testdata directories

[johanbrandhorst]

Hi!

Thanks for this project. I found that it wasn't properly uploading nested testdata structures. I think you might need to add the packages path to the upload action, as when running fuzzing against a package the failing corpus is added to a testdata folder in that package. For example:

When running with packages: ./my/library/path and there is a fuzz failure, the fuzz failure is written to a folder like ./my/library/path/testdata/fuzz/FuzzFoo/beaed54bcc49cf987bf1995eacd23a30662c8da552ab0eeaea0e0540e2df24aa, but the action tries to upload the contents of the ./testdata directory.

Alternatively, perhaps the upload action could upload all testdata/fuzz folders?

[jidicula]

Thanks for this feedback @johanbrandhorst! I've opened up a PR at #8 - if you like, you can try out the action pointing to that branch (uses: jidicula/go-fuzz-action@jidicula/issue-6) in your workflow file. Let me know if that addresses the issue correctly and I'll merge the PR.

[johanbrandhorst]

Thanks for the quick turnaround :). We've replaced our use of the action with a custom implementation for now, so we won't be able to test the changes.