-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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(*): add actions/labeler to label automatically to recognize scope of Pull Request easily #6917
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 11b5a50. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution
Sent with 💌 from NxCloud. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 11b5a50:
|
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #6917 +/- ##
=======================================
Coverage 41.29% 41.29%
=======================================
Files 180 180
Lines 7193 7193
Branches 1454 1454
=======================================
Hits 2970 2970
Misses 3836 3836
Partials 387 387 |
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
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.
@TkDodo I updated now
This actions/labeler will label what package scope is on each Pull Request automaticallly. After this Pull Request merged, labeler can know what package scope have been changed by directory
This action is supported by GitHub Actions officially too like actions/setup-node
Example screenshot
Expectation
I am expecting each maintainers can recognize each Pull Request's package scope by labels of it more easily.