-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ci: Create Bitrise status check for commits #8842
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8842 +/- ##
=======================================
Coverage 45.51% 45.51%
=======================================
Files 1275 1275
Lines 31208 31208
Branches 3187 3187
=======================================
+ Hits 14203 14204 +1
+ Misses 16164 16163 -1
Partials 841 841 ☔ View full report in Codecov by Sentry. |
|
|
…trise-custom-status-check
…trise-custom-status-check
|
|
|
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.
AWESOME!! LGTM!
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.
LGTM
|
Description
The Bitrise E2E check action is currently broken on main. The broken piece is that the check itself isn't re-running after the Bitrise comment is updated. This is because issue_comment doesn't trigger a re-run on the PR itself.
We will see two items appear under Github checks in the PRs.
Run Bitrise E2E Check
- which is an action that handles both starting Bitrise E2E tests and checking for build statusesBitrise E2E Status
- which is a status check that the Run Bitrise E2E Check creates based Bitrise's build status. Depending on the build status, this will either be in a pending, success, or failed state.Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist