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 actions/labeler for v5 #557

Merged
merged 1 commit into from
Dec 6, 2023
Merged

fix actions/labeler for v5 #557

merged 1 commit into from
Dec 6, 2023

Conversation

bjlittle
Copy link
Owner

@bjlittle bjlittle commented Dec 5, 2023

🚀 Pull Request

Description

This pull-request updates the .github/labeler.yml inline with the breaking changes introduced by v5.

Reference https://github.com/actions/labeler/tree/v5.0.0#breaking-changes-in-v5.


Copy link
Collaborator

@tkoyama010 tkoyama010 left a comment

Choose a reason for hiding this comment

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

Thanks. Let's try this.

Copy link

codecov bot commented Dec 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b6108fb) 94.88% compared to head (5a45312) 94.88%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #557   +/-   ##
=======================================
  Coverage   94.88%   94.88%           
=======================================
  Files         119      119           
  Lines        4730     4730           
=======================================
  Hits         4488     4488           
  Misses        242      242           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tkoyama010 tkoyama010 merged commit 036b8d5 into main Dec 6, 2023
15 of 16 checks passed
@tkoyama010 tkoyama010 deleted the fix-labeler branch December 6, 2023 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants