-
Notifications
You must be signed in to change notification settings - Fork 246
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
feat_: implement PR review workflow #5877
base: develop
Are you sure you want to change the base?
Conversation
Jenkins BuildsClick to see older builds (38)
|
bfe0b66
to
8a90758
Compare
Looks like you have BREAKING CHANGES in your PR. Check-list
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## develop #5877 +/- ##
===========================================
+ Coverage 45.91% 46.06% +0.14%
===========================================
Files 888 888
Lines 157381 157379 -2
===========================================
+ Hits 72267 72495 +228
+ Misses 77010 76567 -443
- Partials 8104 8317 +213
Flags with carried forward coverage won't be shown. Click here to find out more. |
da41420
to
54ff2e6
Compare
|
||
on: | ||
pull_request_review: | ||
types: [submitted] |
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.
We probably want all 3 event types:
types: [submitted] | |
types: | |
- submitted | |
- edited | |
- dismissed |
name: PR Review Workflow for Breaking Changes | ||
|
||
on: | ||
pull_request_review: |
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.
Just realised that we probably still need pull_request: [opened]
here, otherwise the check won't appear until some review appear.
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.
Also, pull_request: [labeled, unlabeled]
will also be needed to track breaking change
add/removal.
Hmmm
So it seems we will have to make the relevant teams inside status-go repository first. |
49a9364
to
0b606e4
Compare
0b606e4
to
6b552c1
Compare
@siddarthkay is it time to review this? Or are you still testing? |
1fb7f36
to
03dc775
Compare
03dc775
to
a3ef631
Compare
Summary
This PR Implements a PR review workflow like this :
breaking_change
label exists on PR.@status-im/desktop-qa
and@status-im/mobile-qa
are asked for review on this PR.@status-im/desktop-qa
and@status-im/mobile-qa
approve that PR the Github action will block the PR.