Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix native config (set to staging) #3598

Merged
merged 1 commit into from
Mar 12, 2025
Merged

Conversation

arjunaj5
Copy link
Contributor

@arjunaj5 arjunaj5 commented Mar 12, 2025

Clickup

https://app.clickup.com

Code Coverage

Please add code coverage here

UI Preview

Please add screenshots for UI changes

Summary by CodeRabbit

  • Chores
    • Updated the iOS build settings to use a staging setup rather than production. This change enables better pre-release testing and ensures that our release process is more robust. While there are no direct user-visible changes, this update strengthens our quality assurance and deployment reliability, ultimately contributing to a smoother end-user experience in forthcoming updates.

@arjunaj5 arjunaj5 requested a review from Chethan-Fyle as a code owner March 12, 2025 10:53
Copy link

gitstream-cm bot commented Mar 12, 2025

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 973/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.

@arjunaj5 arjunaj5 requested a review from bistaastha March 12, 2025 10:53
Copy link

coderabbitai bot commented Mar 12, 2025

Walkthrough

This pull request updates the iOS build configuration in the GitHub Actions workflows. The native-config parameter is changed from prod to staging in two workflow files, thereby shifting the build environment from production to staging. Simple and effective—like a true boss move on the configuration front.

Changes

Files Change Summary
.../appflow-release-branch.yml
.../manual-appflow-1.yml
Updated native-config parameter from prod to staging in the iOS build steps

Possibly related PRs

Suggested labels

size/XS

Suggested reviewers

  • mvaishnavi
  • Chethan-Fyle
  • bistaastha

Poem

In the realm of code, the change is pure dynamite,
With staging now set, the build shines bright.
A switch so slick, like a boss’s decree,
Each workflow now flows with the power of 'staging'—you see!
The code steps forward, bold and unconfined,
Punching through limits with a Rajinikanth state of mind!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b47ef74 and 2689f2b.

📒 Files selected for processing (2)
  • .github/workflows/appflow-release-branch.yml (1 hunks)
  • .github/workflows/manual-appflow-1.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (2)
.github/workflows/manual-appflow-1.yml (1)

44-44: Staging is the New Superstar, Brother!
The update to native-config: staging in the iOS build step is exactly what we need to roll out our staging builds with style. This change sets the build target correctly, ensuring our app flows in the right environment—just like the magic of Rajinikanth!

.github/workflows/appflow-release-branch.yml (1)

42-42: Staging Mode Activated, Rajini Style!
The shift to native-config: staging in the iOS build step is a masterstroke. It aligns the build process with the staging environment seamlessly, ensuring our release branch gets the right configuration power. True that, brother—this is how a champion sets the stage!


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @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.

@github-actions github-actions bot added the size/XS Extra Small PR label Mar 12, 2025
Copy link

PR description must contain a link to a ClickUp (case-insensitive)

@arjunaj5 arjunaj5 requested a review from mvaishnavi March 12, 2025 10:54
Copy link

Unit Test Coverage % values
Statements 95.65% ( 19647 / 20540 )
Branches 93.37% ( 7457 / 7986 )
Functions 94.11% ( 5901 / 6270 )
Lines 95.73% ( 19082 / 19933 )

@arjunaj5 arjunaj5 merged commit 0ea0d1a into master Mar 12, 2025
6 of 7 checks passed
arjunaj5 added a commit that referenced this pull request Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Extra Small PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants