fix: TBP for the invalid usage of GH workflow_dispatch action

[abhvsn]

Description

PR to fix invalid usage of workflow_dispatch action.

Automation

/ok-to-test tags=""

🔍 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

• Chores
  • Updated workflow configuration for improved accuracy in invoking processes based on the release branch.
  • Specified the runner environment to enhance build reliability.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the workflow configuration in the .github/workflows/test-build-docker-image.yml file. The changes involve updating the job settings for the invoke-tbp-workflow-for-pg to run on the ubuntu-latest environment and refining the branch reference in the inputs parameter to specify refs/heads/pg. These adjustments aim to enhance the clarity and accuracy of the workflow invocation process on the release branch.

Changes

File	Change Summary
.github/workflows/test-build-docker-image.yml	Modified job configuration to use runs-on for ubuntu-latest and updated inputs to reference refs/heads/pg.

Possibly related PRs

• chore: Trigger TBP on pg for scheduled run on release #36399: This PR also modifies the .github/workflows/test-build-docker-image.yml file, introducing a job that triggers on the release branch, closely related to the current changes.

Suggested labels

skip-changelog, ok-to-test

Poem

In the land of code, a change took flight,
A workflow refined, now clearer and bright.
With ubuntu-latest, it stands tall,
Branches specified, answering the call.
So let’s celebrate this coding delight,
A smoother process, oh what a sight! 🎉

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 115ed5a and d4aa58b.

Files selected for processing (1)

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

Additional comments not posted (1)

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

65-71: Great job on improving the workflow configuration! 🌟

The changes to the invoke-tbp-workflow-for-pg job enhance its clarity and specificity:

1. Using runs-on to specify a dedicated runner environment (ubuntu-latest) ensures a consistent execution context for the job.

2. Updating the branch reference in the inputs parameter to use the full branch name (refs/heads/pg) improves the accuracy and eliminates any potential ambiguity.

These modifications contribute to a more robust and maintainable workflow. 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.