Fix the failing release workflow by adding a call to true after grepping
for the hopefully nonexistent release tag.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Cleanup the .github actions:
- Use the same syntax and/or commands where possible
- Drop unnecessary parameters and steps / commands
- In the all-green job ensure that all CI jobs passed
- Update the naming of jobs
- Review permissions and grant write permission only where
necessary (repo is set to read-only by default)
- Review installed dependencies (try to fix the failing docs job)
- Run yamllint and fix findings
- Replace deprecated set-output syntax
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Use Python 3.9 - 3.12 and Ansible 2.14 - 2.16, devel and milestone to run
tests of the collection. Use the latest stable python version in test setups
where sensible. Instead of using the integration.yml workflog from main
use it from the same commit as the test runs instead.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Bump the versions of all used actions to the latest stable version and
try to use the same config across files and defaults where sensible.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
To bypass restrictions on GitHub Actions run the docs and ci workflows
manually after creating a release. GitHub Actions does not trigger
other workflows from a workflow run if not using a personal access
token (PAT). By calling the workflows explicitly, it is possible to
work around this restriction without the need for a PAT.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
