Triggering testing workflows when there are changes on the workflows

[pacostas]

Summary

This PR adds a hook in order to trigger the workflows while there are changes on the workflow itself

Use Cases

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[pacostas]

@paketo-buildpacks/java-maintainers The java sample integration tests seems like they are failing.

[dmikusa]

@pacostas There is a script that runs for the Java integration tests. The script looks at the changes and determines which samples to run for the integration test. Because there are so many Java samples, we don't want to run all the samples if a change was isolated to just one sample.

This change is breaking that script. I'm not sure why offhand, but I'd suspect it's based on the inputs changing. There's likely an assumption about the inputs will be under the java/ section, but this means they could be under .github/.

The easiest thing is to add set -x into the bash code, so we can see what it's doing.

samples/.github/workflows/test-pull-request-java.yml

Line 25 in b4eca16

set -eo pipefail

That bash will likely need adjusted to work with this new scenario.