feat: trust github-actions bot for virt-platform-autopilot

[tiraboschi]

Add github-actions to the trusted_apps list so that PRs opened by the github-actions[bot] (e.g. automated CRD sync) skip the needs-ok-to-test gate and have CI triggered automatically.

Summary

This PR enables automated CI triggering for the virt-platform-autopilot repository by adding the github-actions bot to the trusted apps list in its Prow configuration.

Changes

File modified: core-services/prow/02_config/openshift-virtualization/virt-platform-autopilot/_pluginconfig.yaml

Added github-actions to the trusted_apps list under the triggers section. This allows PRs opened by the GitHub Actions bot (for example, automated CRD synchronization) to bypass the manual needs-ok-to-test approval gate and have CI automatically triggered.

Previously, only openshift-merge-bot was configured as a trusted app for this repository. The change allows automated workflows to streamline the CI process without requiring manual approval for each automation-generated PR.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 09081abe-f689-4b02-ab0f-b2684ce706b2

📥 Commits

Reviewing files that changed from the base of the PR and between ce0233c and c4ffe09.

📒 Files selected for processing (1)

• core-services/prow/02_config/openshift-virtualization/virt-platform-autopilot/_pluginconfig.yaml

---

Walkthrough

This PR adds github-actions to the trusted applications list in the virt-platform-autopilot Prow plugin configuration, enabling GitHub Actions workflows to trigger Prow jobs without additional authorization checks.

Changes

Prow Plugin Configuration Update

Layer / File(s)	Summary
Trust GitHub Actions in plugin triggers core-services/prow/02_config/openshift-virtualization/virt-platform-autopilot/_pluginconfig.yaml	Adds github-actions to the trusted_apps list under triggers to permit GitHub Actions as an authorized workflow trigger.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding github-actions as a trusted bot for the virt-platform-autopilot configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The custom check for Ginkgo test names is not applicable. This PR modifies only a YAML configuration file, not Go code or Ginkgo tests. The repository contains no test files.
Test Structure And Quality	✅ Passed	Custom check targets Ginkgo test code quality. This PR only modifies a YAML configuration file. No test files are included, so the check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies a Prow plugin config YAML file; no Ginkgo e2e tests are added. MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies a Prow plugin configuration YAML file to trust github-actions. No new Ginkgo e2e tests are added, so the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies a Prow CI/CD plugin configuration file, not deployment manifests, operator code, or controllers. The topology-aware scheduling check is not applicable to CI configuration files.
Ote Binary Stdout Contract	✅ Passed	PR modifies only a YAML Prow configuration file. The OTE Binary Stdout Contract check applies only to source code and test binaries. Configuration files are not subject to this check.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR modifies only a prow configuration YAML file, not adding any Ginkgo e2e tests. The custom check explicitly applies to "when new Ginkgo e2e tests are added" and is not applicable to this PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@tiraboschi: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

@tiraboschi: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[tiraboschi]

/lgtm
/approve

[openshift-ci]

@tiraboschi: you cannot LGTM your own PR.

Details

In response to this:

/lgtm
/approve

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[nirdothan]

Thank you

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nirdothan, tiraboschi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/prow/02_config/openshift-virtualization/virt-platform-autopilot/OWNERS [tiraboschi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment