ci: Run server tests on pg branch

[sharat87]

Summary by CodeRabbit

• Chores
  • Updated workflow conditions to ensure PostgreSQL build is triggered when the pull request head reference is 'pg'.
  • Simplified logic to unconditionally start the PostgreSQL container in the build process.

[coderabbitai]

Walkthrough

The changes enhance the CI/CD workflows for a project by refining conditions for running jobs. Specifically, checks for PostgreSQL builds in the quality checks workflow now include the head reference in pull requests, and the server build workflow is simplified by removing conditional checks, ensuring the PostgreSQL container always starts.

Changes

Files	Change Summary
.github/workflows/quality-checks.yml	Updated is-pg-build condition to include head reference in pull requests.
.github/workflows/server-build.yml	Simplified logic to always start the PostgreSQL container, regardless of conditions.

Poem

In our code, new rules now reside,
Checking heads hands side by side.
PostgreSQL starts on each new day,
Simplicity lights the coder’s way.
🐇✨ Code flows smoother, no more dread,
Our builds now easily sped. 🚀

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

.github/workflows/server-build.yml (1)

Line range hint 173-174: Security Issue: Potential exposure of HashiCorp Terraform password.

It appears there might be a security risk related to the exposure of a HashiCorp Terraform password. It's crucial to ensure that sensitive credentials are securely managed and not exposed in the workflow files.

Please verify this finding and, if confirmed, consider using GitHub secrets or other secure storage mechanisms to handle sensitive data.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 979f44b and 41a6eee.

Files selected for processing (2)

• .github/workflows/quality-checks.yml (1 hunks)
• .github/workflows/server-build.yml (1 hunks)

Additional context used

Gitleaks

.github/workflows/server-build.yml

173-174: Identified a HashiCorp Terraform password field, risking unauthorized infrastructure configuration and security breaches. (hashicorp-tf-password)

Additional comments not posted (2)

.github/workflows/quality-checks.yml (1)

48-48: Approved: Updated condition for PostgreSQL builds.

The change to include both base.ref and head.ref in the condition for PostgreSQL builds is a good enhancement. It ensures that the PostgreSQL-specific checks are run more comprehensively, aligning with the PR's objectives.

.github/workflows/server-build.yml (1)

142-145: Approved: Simplified PostgreSQL container setup.

The updated condition and command to start the PostgreSQL container are straightforward and clear. Removing additional complexity from the workflow is beneficial for maintainability and clarity.