Support Depends-On

[abikouo]

This github action allows to override the version of a collection to checkout based on keyword depends-on from pull request title
Extracted from #45

[abikouo]

@Qalthos this one the feature extracted from #45
closes #49

[Qalthos]

Okay, can you replace the checkout step

[Qalthos]

Not with my fork, obviously, but can you update the existing workflows to switch to this instead of checkout? changelog and safe-to-test shouldn't need to be updated, but the rest would benefit from having it.

cf. Qalthos@8a31c25

[abikouo]

Not with my fork, obviously, but can you update the existing workflows to switch to this instead of checkout? changelog and safe-to-test shouldn't need to be updated, but the rest would benefit from having it.

cf. Qalthos@8a31c25

The only workflow which can benefit from this action is integration.yml, this action is used to checkout dependency only (It has been updated accordingly), this is why the repository parameter is required, we don't want to add depends-on in a repository being checkout

[Qalthos]

The only workflow which can benefit from this action is integration.yml, this action is used to checkout dependency only (It has been updated accordingly), this is why the repository parameter is required, we don't want to add depends-on in a repository being checkout

But this can absolutely be used to depends-on a PR that fixes sanity tests, for example. It's a contrived situation, but https://github.com/ansible-collections/ansible.utils/pull/248/checks?check_run_id=12373927044 and https://github.com/ansible-collections/ansible.utils/pull/248/checks are runs of the same checks with and without depends-on where another PR is fixing the underlying issue.

[abikouo]

The only workflow which can benefit from this action is integration.yml, this action is used to checkout dependency only (It has been updated accordingly), this is why the repository parameter is required, we don't want to add depends-on in a repository being checkout

But this can absolutely be used to depends-on a PR that fixes sanity tests, for example. It's a contrived situation, but https://github.com/ansible-collections/ansible.utils/pull/248/checks?check_run_id=12373927044 and https://github.com/ansible-collections/ansible.utils/pull/248/checks are runs of the same checks with and without depends-on where another PR is fixing the underlying issue.

all workflows have been updated with checkout_repository