chore: Added pg branch

[sagar-qa007]

Description

Run the CI test limit in PG branch

Fixes #36085

Automation

/ok-to-test tags="@tag.Sanity"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10683137823
Commit: 288bb1a
Cypress dashboard.
Tags: @tag.Sanity
Spec:

---

Tue, 03 Sep 2024 13:03:06 UTC

Communication

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

• Yes
• No

Summary by CodeRabbit

• New Features
  • Introduced a new output variable is-pg-build to enhance build handling based on pull request base branches.
  • Improved workflow logic to conditionally manage builds depending on the pull request context.

[coderabbitai]

Walkthrough

The changes introduce a new output variable, is-pg-build, to two GitHub Actions workflow files. This variable assesses whether the base reference of a pull request is 'pg', enhancing the workflows' ability to conditionally manage builds based on the pull request's context. The variable is utilized in the client-build job, allowing for improved control flow in the build process.

Changes

Files	Change Summary
.github/workflows/build-client-server-*.yml	Added is-pg-build output variable to both workflows, allowing conditional handling of builds based on the pull request's base branch.

Poem

In workflows where builds take flight,
A new variable shines so bright.
is-pg-build now guides the way,
With branches checked, it leads the play.
Conditional flows, a dance so neat,
In GitHub's realm, we can't be beat! 🌟

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f02b448 and 288bb1a.

Files selected for processing (2)

• .github/workflows/build-client-server-count.yml (3 hunks)
• .github/workflows/build-client-server.yml (3 hunks)

Additional comments not posted (5)

.github/workflows/build-client-server.yml (3)

17-17: Great job introducing the is-pg-build output variable! 👍

The is-pg-build output variable is correctly set based on the condition that checks if the base reference of the pull request is 'pg'. This will allow subsequent jobs to conditionally perform actions based on the pull request's context.

---

31-31: Excellent work setting the is-pg-build output variable! 🌟

The is-pg-build output variable is correctly set in the args step based on the condition that checks if the base reference of the pull request is 'pg'. This ensures that the variable is available for subsequent jobs to use.

---

97-97: Nicely done passing the is-pg-build output variable to the server-build job! 🙌

By passing the is-pg-build output variable from the file-check job to the server-build job, you enable the server-build job to conditionally perform actions based on the pull request's context. This enhances the flexibility and control flow of the build process.

.github/workflows/build-client-server-count.yml (2)

33-33: Great job adding the is-pg-build output variable! 👍

The code segment correctly sets the is-pg-build output variable based on the condition github.event.client_payload.pull_request.base.ref == 'pg'. This variable can be used in subsequent jobs to conditionally manage the build process based on the pull request's context.

---

111-111: Excellent work passing the is-pg-build variable to the server-build job! 🙌

The code segment correctly passes the is-pg-build variable as an input to the server-build job. This allows the server-build job to access the value of the is-pg-build variable and use it to conditionally manage the build process based on the pull request's context.