chore: Modify inputs for TBP workflow_dispatch on pg branch

[abhvsn]

Description

Automation

/test sanity

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• New Features
  • Enhanced GitHub Actions workflow to support dynamic inputs for improved flexibility.
  • Introduced new parameters for tags and ted_tag to adapt to various configurations.

[coderabbitai]

Walkthrough

The pull request introduces changes to the GitHub Actions workflow defined in the test-build-docker-image.yml file. It modifies the inputs for the workflow-dispatch action, replacing a static JSON string with dynamic values for tags and ted_tag. Additionally, the ref parameter is explicitly set to refs/heads/pg, enhancing the workflow's configurability.

Changes

File	Change Summary
.github/workflows/test-build-docker-image.yml	Modified inputs in workflow-dispatch from a static JSON string to dynamic values for tags and ted_tag; added ref parameter set to refs/heads/pg.

Possibly related PRs

• chore: Trigger TBP on pg for scheduled run on release #36399: Involves modifications to the .github/workflows/test-build-docker-image.yml file, related to job configuration and branch handling.
• fix: TBP for the invalid usage of GH workflow_dispatch action #36429: Focuses on the workflow_dispatch action and clarifying branch references in the .github/workflows/test-build-docker-image.yml file.

Suggested labels

skip-changelog, ok-to-test

Poem

In the workflow's dance, a change we see,
Dynamic tags now set, oh what glee!
With branches defined, clear as day,
Our CI/CD flows in a better way.
Let’s build and test, let’s make it right,
Cheers to the code, shining bright! 🌟

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3bc73f5 and a6ea892.

Files selected for processing (1)

• .github/workflows/test-build-docker-image.yml (1 hunks)

Additional comments not posted (2)

.github/workflows/test-build-docker-image.yml (2)

71-71: Great work on making the workflow inputs more dynamic! 👍

By sourcing the tags value from the output of a previous job and the ted_tag value from the workflow's inputs, you've made this workflow much more flexible and configurable. This is a smart way to enhance the reusability of the workflow.

---

72-72: Excellent job on explicitly setting the branch reference! 🌟

By setting the ref parameter to refs/heads/pg, you've made it crystal clear which branch this workflow dispatch is targeting. This eliminates any potential ambiguity and ensures the workflow runs on the intended branch. Well done!

---

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 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.

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.