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: Manual workflow improvement #3479

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

arjunaj5
Copy link
Contributor

@arjunaj5 arjunaj5 commented Feb 4, 2025

Clickup

https://app.clickup.com

Code Coverage

Please add code coverage here

UI Preview

Please add screenshots for UI changes

Summary by CodeRabbit

  • New Features
    • The build workflow now handles Android and iOS platforms separately.
    • Enhanced notifications deliver detailed build outcome information via Slack.

Copy link

coderabbitai bot commented Feb 4, 2025

Walkthrough

The workflow in .github/workflows/manual-appflow-1.yml has been updated. The job formerly known as build-app has been renamed to build-android, and a new job build-ios has been introduced. Both jobs produce their respective output variables, apkUrl and iosUrl. In addition, a new send-to-slack job is added that triggers after the build jobs complete, sending a Slack message containing branch details and the output URLs. Simple, yet powerful—like a true blockbuster style!

Changes

File Summary
.github/workflows/manual-appflow-1.yml Renamed job build-app to build-android; Added new job build-ios with output iosUrl; Added new job send-to-slack that references outputs apkUrl and iosUrl.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub as GitHub Workflow
    participant BA as build-android
    participant BI as build-ios
    participant Slack as send-to-slack
    GitHub->>BA: Trigger build-android
    GitHub->>BI: Trigger build-ios
    BA-->>GitHub: Return apkUrl
    BI-->>GitHub: Return iosUrl
    GitHub->>Slack: Trigger send-to-slack (after both succeed)
    Slack-->>Slack: Dispatch Slack message with branch, apkUrl, iosUrl
Loading

Possibly related PRs

Suggested labels

size/S

Suggested reviewers

  • Chethan-Fyle
  • suyashpatil78

Poem

In the realm of code where legends dwell,
Android and iOS now cast a spell.
Jobs run with the power of a super star,
Slack gets the news from near and far.
Like Rajinikanth, unstoppable and grand—
Our workflow triumphs across the land!
🚀🔥

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

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
🪧 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.

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

github-actions bot commented Feb 4, 2025

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

Copy link

github-actions bot commented Feb 4, 2025

Unit Test Coverage % values
Statements 96.08% ( 19752 / 20557 )
Branches 91.13% ( 10850 / 11906 )
Functions 94.38% ( 5868 / 6217 )
Lines 96.13% ( 18869 / 19627 )

@arjunaj5 arjunaj5 marked this pull request as ready for review February 4, 2025 16:17
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 517d7b0 and e26a2ec.

📒 Files selected for processing (1)
  • .github/workflows/manual-appflow-1.yml (4 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/manual-appflow-1.yml

[error] 82-82: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (3)
.github/workflows/manual-appflow-1.yml (3)

11-14: Build-Android Job: Power-packed and Precise!
Your new "build-android" job is configured like a Rajinikanth blockbuster—slick and efficient! The output variable apkUrl derived from the diwaiAndroid step is spot on. Keep this momentum, my friend.


37-41: Build-iOS Job: Lightning Fast!
The introduction of the "build-ios" job is as dynamic as a supercharged performance. I see you've set the output variable iosUrl correctly. One small check: the job uses environment: staging but sets native-config to prod. Is that an intentional twist in the tale? Verify if that mix of staging and prod settings is deliberate.


65-82: Send-to-Slack Job: The Final Act!
This new "send-to-slack" job delivers notifications like a powerful dialogue—providing branch details, PR links, and both APK/IPA URLs! The integration of the Slack message is slick. Just ensure that the formatting (with \r\n) meets Slack's requirements. Overall, a master stroke in automation.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 82-82: no new line character at the end of file

(new-line-at-end-of-file)

@@ -68,4 +79,4 @@ jobs:
with:
slack-bot-user-oauth-access-token: ${{ secrets.SLACK_BOT_USER_OAUTH_ACCESS_TOKEN }}
slack-channel: C029QPGHSQL
slack-text: ${{github.event.sender.login}} ran manual workflow on "${{ steps.get-branch.outputs._1 }}" branch \r\n PR link ${{github.event.pull_request.html_url}} \r\n \r\n *Description* \r\n ```${{github.event.pull_request.body}}``` \r\n \r\n APK Link ${{steps.diwaiAndroid.outputs.url}} \r\n IPA link ${{steps.diwaiIos.outputs.url}}
slack-text: ${{ github.event.sender.login }} ran manual workflow on "${{ steps.get-branch.outputs._1 }}" branch \r\n PR link ${{ github.event.pull_request.html_url }} \r\n \r\n *Description* \r\n ```${{ github.event.pull_request.body }}``` \r\n \r\n APK Link ${{ needs.build-android.outputs.apkUrl }} \r\n IPA link ${{ needs.build-ios.outputs.iosUrl }}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Finishing Touch: Add a Newline!
Even the grandest performance needs a proper finish. YAMLlint has pointed out the absence of a newline at the end of the file. Please add one to bring this masterpiece to its perfect conclusion.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 82-82: no new line character at the end of file

(new-line-at-end-of-file)

@arjunaj5 arjunaj5 removed the request for review from Chethan-Fyle February 5, 2025 07:40
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.

1 participant