-
Notifications
You must be signed in to change notification settings - Fork 15
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
base: master
Are you sure you want to change the base?
Conversation
WalkthroughThe workflow in Changes
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
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Tip 🌐 Web search-backed reviews and chat
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
PR description must contain a link to a ClickUp (case-insensitive) |
|
There was a problem hiding this 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
📒 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 variableapkUrl
derived from thediwaiAndroid
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 variableiosUrl
correctly. One small check: the job usesenvironment: staging
but setsnative-config
toprod
. 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 }} |
There was a problem hiding this comment.
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)
Clickup
https://app.clickup.com
Code Coverage
Please add code coverage here
UI Preview
Please add screenshots for UI changes
Summary by CodeRabbit