ci(helm-unittest): use repo and ref from PR HEAD

[prashant-shahi]

CI

-helm-unittest: use repo and ref from PR HEAD

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration to improve pull request checkout process
  • Enhanced workflow's ability to dynamically reference pull request branches and repositories

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow file .github/workflows/helm-unittest.yaml by enhancing the self-checkout step. The changes introduce dynamic repository and reference parameters using GitHub context variables. These modifications allow the workflow to automatically checkout the specific branch and repository associated with the pull request being processed, providing more flexibility in the workflow's execution.

Changes

File	Change Summary
.github/workflows/helm-unittest.yaml	Added ref and repository parameters to self-checkout step using GitHub pull request context variables

Possibly related PRs

• feat(github): point to ref/repo from PR HEAD, add/remove labels #10: Similar self-checkout step parameter additions in other GitHub Actions workflows
• fix(github): use env and compacted JSON for github-trigger input #9: Modifications to github-trigger workflow involving workflow context
• feat(github): primus workflow to verify membership and trigger workflow #8: Introduction of self-checkout step in a new workflow

Suggested reviewers

• grandwizard28

Poem

🐰 A Workflow's Whisker-Twitch

Checkout branches with a hop and a switch,
GitHub context, a magical stitch,
Pull requests dance, code takes flight,
Workflows singing with pure delight!

🚀✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 11ae06a and 61bb2b8.

📒 Files selected for processing (1)

• .github/workflows/helm-unittest.yaml (1 hunks)

🔇 Additional comments (1)

.github/workflows/helm-unittest.yaml (1)

28-30: Verify behavior with fork PRs and suggest adding fallbacks.

The changes correctly use the PR's head ref and repository, which is essential for testing the exact code from the PR. However, consider these edge cases:

1. When the PR is from a fork repository, ensure the workflow has necessary permissions
2. If the PR branch is deleted during workflow execution
3. When triggered outside PR context (e.g., manual workflow dispatch)

Add fallback values for safety:

 with:
-  ref: ${{ github.event.pull_request.head.ref }}
-  repository: ${{ github.event.pull_request.head.repo.full_name }}
+  ref: ${{ github.event.pull_request.head.ref || github.ref }}
+  repository: ${{ github.event.pull_request.head.repo.full_name || github.repository }}

Let's verify the current workflow behavior:

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.