Repository navigation
ci: use shared actions and lock workflow dependencies - #278
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
CI tests do not run automatically on pull requests. A role repository See GitHub CI testing using /citest Run every available CI workflow: Run the linting and other lightweight checks: Run the integration tests (QEMU/container and Testing Farm): Run one or more selected workflows by separating their names with spaces:
Post another |
Small third-party actions create recurring dependency updates across role repositories. Replace them with composite actions in linux-system-roles/.github. Implement commit status, release, pull request, and other workflow operations with git, gh, Bash, and Python. Use pinned official GitHub actions for checkout and artifact transfer, and retain the upstream actions needed for CodeQL, Codecov, codespell, setup-python, and Testing Farm. Update the role workflow templates to use the shared actions. Document the publishing order so the actions are available before the templates are rolled out to role repositories. Generate an actions.lock file for each managed role repository. Limit organization workflows to GitHub-owned and selected external actions, and require SHA pinning. Locked commits satisfy the pinning rule for workflows covered by an actions.lock file. Assisted-by: Codex using model Sol medium 6 Signed-off-by: Rich Megginson <rmeggins@redhat.com>
Small third-party actions create recurring dependency updates across
role repositories. Replace them with composite actions in
linux-system-roles/.github. Implement commit status, release, pull
request, and other workflow operations with git, gh, Bash, and Python.
Use pinned official GitHub actions for checkout and artifact transfer,
and retain the upstream actions needed for CodeQL, Codecov, codespell,
setup-python, and Testing Farm.
Update the role workflow templates to use the shared actions. Document
the publishing order so the actions are available before the templates
are rolled out to role repositories.
Generate an actions.lock file for each managed role repository. Limit
organization workflows to GitHub-owned and selected external actions,
and require SHA pinning. Locked commits satisfy the pinning rule for
workflows covered by an actions.lock file.
Assisted-by: Codex using model Sol medium 6
Signed-off-by: Rich Megginson rmeggins@redhat.com