disabled image build and deploy for care stagin

[tellmeY18]

Summary by CodeRabbit

• Deployment
  • Removed staging deployment job
  • Updated build job conditions to run only on develop branch and version tags
  • Simplified deployment workflow configuration

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions deployment workflow configuration in .github/workflows/deploy.yaml. The primary changes involve removing the deploy-staging-gcp job and adjusting the conditions for the build job. The workflow now restricts the build process to only run on the develop branch or when a tag starting with v is pushed, effectively removing the previous staging branch deployment option.

Changes

File	Change Summary
.github/workflows/deploy.yaml	- Removed deploy-staging-gcp job - Modified build job condition to exclude refs/heads/staging - Restricted build to develop branch and tags starting with v

Poem

🐰 Deployment dance, a workflow's new beat
Staging steps now retreat
Develop and tags take the stage
Streamlined CI, turning the page
A rabbit's code, lean and bright! 🚀

---

📜 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 83a115d and d697302.

📒 Files selected for processing (1)

• .github/workflows/deploy.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: Test
• GitHub Check: cypress-run (1)
• GitHub Check: OSSAR-Scan
• GitHub Check: CodeQL-Build
• GitHub Check: OSSAR-Scan

🔇 Additional comments (1)

.github/workflows/deploy.yaml (1)

64-64: 🛠️ Refactor suggestion

Remove or update references to the 'staging' branch and tags to ensure consistency.
Although the build job no longer runs on the staging branch, there are still references to 'staging' in push triggers, pull request triggers, and Docker tags. If the intention is to fully disable staging builds, you can remove these references for clarity. Conversely, if staging-related tags are still relevant (e.g., for environment tagging), consider implementing a dedicated step to handle them.

Example patch removing staging references in Docker tags (for demonstration only):

-            type=raw,value=staging-latest,enable=${{ github.ref == 'refs/heads/staging' }}
-            type=raw,value=staging-latest-${{ github.run_number }}-{{date 'YYYYMMDD'}}-{{sha}},enable=${{ github.ref == 'refs/heads/staging' }}

Likely invalid or redundant comment.

---

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.

[netlify]

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	d697302
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/677b727645c8510008a62bab
😎 Deploy Preview	https://deploy-preview-9779--care-ohc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cloudflare-workers-and-pages]

Deploying care-fe with    Cloudflare Pages

Latest commit:	d697302
Status:	✅  Deploy successful!
Preview URL:	https://932a6ed3.care-fe.pages.dev
Branch Preview URL:	https://vysakh-update-staging.care-fe.pages.dev

View logs

[cypress]

CARE    Run #4164

Run Properties:   Failed #4164  •  d69730282c: disabled image build and deploy for care stagin

Project	CARE
Branch Review	vysakh/update-staging
Run status	Failed #4164
Run duration	01m 48s
Commit	d69730282c: disabled image build and deploy for care stagin
Committer	Vysakh Premkumar
View all properties for this run ↗︎

---

Test results
Failures	1
Flaky	0
Pending	0
Skipped	0
Passing	3
View all changes introduced in this branch ↗︎

---

Tests for review

  cypress/e2e/patient_spec/patient_search.cy.ts • 1 failed test

View Output

Test		Artifacts
Patient Search > search patient with phone number and verifies details		Test Replay Screenshots

[github-actions]

@tellmeY18 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌