Skip to content

Enable TriggerGitHubWorkflows for openshift-eng/ai-helpers#74538

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
cblecker:enable-trigger-github-workflows-ai-helpers
Feb 9, 2026
Merged

Enable TriggerGitHubWorkflows for openshift-eng/ai-helpers#74538
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
cblecker:enable-trigger-github-workflows-ai-helpers

Conversation

@cblecker
Copy link
Member

@cblecker cblecker commented Feb 6, 2026

Summary

Enable the Prow trigger_github_workflows option for the openshift-eng/ai-helpers repository to ensure GitHub Actions workflows are properly triggered when handling pull requests.

Changes

  • Added triggers: section to core-services/prow/02_config/openshift-eng/ai-helpers/_pluginconfig.yaml
  • Enabled trigger_github_workflows: true to allow Prow to trigger GitHub Actions workflows
  • Included dependabot as a trusted app (matching the repository's .github/dependabot.yml configuration)

Context

The openshift-eng/ai-helpers repository has branch protection requiring lint and check-version-bump status checks, which are GitHub Actions workflows. Enabling trigger_github_workflows ensures these workflows are properly triggered by Prow, satisfying the branch protection requirements.

This follows the same pattern already used in backube/volsync.

Verification

  • ✓ Prow configuration validated with make prow-config
  • ✓ YAML structure matches the reference implementation

Add trigger_github_workflows configuration to allow Prow to trigger GitHub
Actions workflows (lint, check-version-bump) when handling PRs. This ensures
branch protection requirements are properly satisfied by Prow.

Configuration follows the same pattern as backube/volsync with dependabot
as the only trusted app.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@cblecker
Copy link
Member Author

cblecker commented Feb 6, 2026

/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

@cblecker: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 6, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@cblecker: 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-robot
Copy link
Contributor

@cblecker: no rehearsable tests are affected by this change

@cblecker
Copy link
Member Author

cblecker commented Feb 7, 2026

/assign @dgoodwin @stbenjam

@stbenjam
Copy link
Member

stbenjam commented Feb 9, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, stbenjam

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:

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

@cblecker
Copy link
Member Author

cblecker commented Feb 9, 2026

/retest-required

@cblecker
Copy link
Member Author

cblecker commented Feb 9, 2026

/test release-controller-config

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

@cblecker: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 56d9916 into openshift:main Feb 9, 2026
10 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

@cblecker: Updated the plugins configmap in namespace ci at cluster app.ci using the following files:

  • key core-services-prow-02_config-openshift-eng-ai-helpers-_pluginconfig.yaml using file core-services/prow/02_config/openshift-eng/ai-helpers/_pluginconfig.yaml
Details

In response to this:

Summary

Enable the Prow trigger_github_workflows option for the openshift-eng/ai-helpers repository to ensure GitHub Actions workflows are properly triggered when handling pull requests.

Changes

  • Added triggers: section to core-services/prow/02_config/openshift-eng/ai-helpers/_pluginconfig.yaml
  • Enabled trigger_github_workflows: true to allow Prow to trigger GitHub Actions workflows
  • Included dependabot as a trusted app (matching the repository's .github/dependabot.yml configuration)

Context

The openshift-eng/ai-helpers repository has branch protection requiring lint and check-version-bump status checks, which are GitHub Actions workflows. Enabling trigger_github_workflows ensures these workflows are properly triggered by Prow, satisfying the branch protection requirements.

This follows the same pattern already used in backube/volsync.

Verification

  • ✓ Prow configuration validated with make prow-config
  • ✓ YAML structure matches the reference implementation

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.

@cblecker cblecker deleted the enable-trigger-github-workflows-ai-helpers branch February 9, 2026 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants