NO-JIRA: clone ai-helpers into workspace for plugin file access

[bryan-cox]

Summary

• Clones ai-helpers into $GITHUB_WORKSPACE/ai-helpers instead of /tmp/ai-helpers
• This puts plugin files within the project directory so Claude Code can read them without permission restrictions

Test plan

• Merge and trigger /test-wif on any open PR

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

This release contains internal infrastructure and tooling updates with no end-user visible changes.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@bryan-cox: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

• Clones ai-helpers into $GITHUB_WORKSPACE/ai-helpers instead of /tmp/ai-helpers
• This puts plugin files within the project directory so Claude Code can read them without permission restrictions

Test plan

• Merge and trigger /test-wif on any open PR

🤖 Generated with Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Please specify an area label

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.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR updates the .github/workflows/claude-wif-test.yaml workflow to relocate the ai-helpers plugin setup from the temporary directory to the GitHub Actions workspace. The "Set up ai-helpers plugins" step now clones openshift-eng/ai-helpers into $GITHUB_WORKSPACE/ai-helpers instead of /tmp/ai-helpers, and the generated known_marketplaces.json is updated to reference the new workspace paths for both the plugin source and install location.

Possibly related PRs

• openshift/hypershift#8611: Both PRs modify the same .github/workflows/claude-wif-test.yaml "Set up ai-helpers plugins" step, changing how openshift-eng/ai-helpers is cloned and how known_marketplaces.json points to that path.
• openshift/hypershift#8609: Both PRs modify the same claude-wif-test.yaml workflow around the ai-helpers setup by changing how/where ai-helpers/plugins are sourced and installed (moving away from /tmp in support of the container-based test runner).
• openshift/hypershift#8614: Both PRs modify the same .github/workflows/claude-wif-test.yaml "Set up ai-helpers plugins" and marketplace setup by cloning openshift-eng/ai-helpers and updating the generated plugin paths (this PR switches to $GITHUB_WORKSPACE, while the retrieved PR uses /tmp).

Suggested reviewers

• csrwng
• Nirshal

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Stable And Deterministic Test Names	❌ Error	Test test/envtest/suite_test.go uses fmt.Sprintf with variable featureSet in Ginkgo test names, violating stability requirement.	Replace fmt.Sprintf test names with static strings; put dynamic values in test body. Use "should install all CRDs for feature set" instead of "should install all CRDs for feature set %q".

✅ Passed checks (10 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: cloning ai-helpers into the workspace instead of /tmp for plugin file access, which aligns with the file modification and PR objectives.
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.
Test Structure And Quality	✅ Passed	Check not applicable: PR only modifies GitHub Actions workflow YAML, not Ginkgo test code. The custom check targets Ginkgo test code quality requirements.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR modifies a GitHub Actions workflow file, not Kubernetes deployment manifests, operator code, or controllers. The custom check does not apply.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies a GitHub Actions workflow YAML file, not Ginkgo e2e tests. Custom check scope requires Ginkgo test declarations (It/Describe/Context/When) which are absent.
No-Weak-Crypto	✅ Passed	The PR modifies only a GitHub Actions workflow YAML file that contains no cryptographic implementations, weak crypto imports (MD5/SHA1/DES/RC4/3DES/Blowfish/ECB), or insecure secret comparisons.
Container-Privileges	✅ Passed	No privileged container directives found in the workflow (no privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation). PR moves away from container-based approaches.
No-Sensitive-Data-In-Logs	✅ Passed	PR changes cloning location to GITHUB_WORKSPACE without introducing logging of sensitive data. Configuration is written to files via redirection, not logged. No new sensitive data exposure.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[bryan-cox]

/test-wif