optionally put assets in separate dir
After fetching a release with several artifact files, I want to use a shell script to iterate over those files in a task. Ideally, the shell code would look something like this:
for i in *; do
do_something_to_an_artifact "$i"
done
The problem is that these artifacts coexist in the same directory with metadata files tag, version, body, timestamp, commit_sha, and url. The * glob will include those metadata files, but I only want it to include the artifacts downloaded from the GitHub release.
So, I propose adding a new boolean source parameter called asset_dir. When enabled, the resource will put the artifacts in a new subdirectory called assets.
I tested my changes with asset_dir unset, and the resource downloaded the artifacts to the same directory as the metadata files, preserving the existing behavior. When I tested my changes with asset_dir set to true, the artifacts ended up in a new subdirectory as expected.
Thank you for reading my pull-request!