-
Notifications
You must be signed in to change notification settings - Fork 502
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
Add support for PR labels #2523
Conversation
Put the labels that are created in text also as GH labels onto the PR via the API.
Make labelling a general operation and implement it for GitLab as well.
Just fixed the broken test – sorry for not running the full test suite locally before, now I need another workflow approval 🙄 |
Codecov Report
@@ Coverage Diff @@
## main #2523 +/- ##
==========================================
- Coverage 81.02% 81.01% -0.02%
==========================================
Files 143 144 +1
Lines 2519 2544 +25
Branches 51 48 -3
==========================================
+ Hits 2041 2061 +20
- Misses 478 483 +5
Continue to review full report at Codecov.
|
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
Long awaited feature! Thanks for implementing it! It would be great to be able to configure (in the repo config) a subset of labels that Scala Steward will create. Some of the labels in the description are currently redundant and not all of them might be relevant to the project's workflow, so creating all of them might be a bit too noisy. |
Glad to hear it's of use to someone 🙂 I thought about the filtering too and imagined this PR's feature could be augmented by some regex or another, maybe more semantic mechanism to filter the labels (not only on the PR, also in the body). But I concluded it deserves a separate PR. Chances are there that I find the time to do it once this one is merged. |
@fthomas Codacy is unhappy about something that only got reformatted and test coverage is on a level where I don't see ways to reasonably improve it further. From my side the PR is hence ready to merge, unless you see something to take care of still? |
Any updates? |
@fthomas Do you have a time to test this with your test Steward instance ?? |
Hi! Is there any update about this? |
Thanks and sorry for keeping you waiting 🙇 |
is this usable through the .scala-steward.conf file ? or in the github action ? |
Depending on how you run Scala Steward, either just add with:
other-args: '--add-labels' to the GitHub action. |
I was not able to make it work with the github action. I think that it is expected to place the argument in the
|
yes ok , i have the same experience with other-args not being valid :/ |
@andresld it would be nice if it was in the |
@ybasket and @andresld , it has been fixed , see: scala-steward-org/scala-steward-action#386 (comment) |
first step for scalameta#4333 Thit commit let scala-steward PRs put Github labels such as `semver-spec-patch`, which will be useful for mergify. see: scala-steward-org/scala-steward#2523 scala-steward-org/scala-steward-action#387
first step for #4333 Thit commit let scala-steward PRs put Github labels such as `semver-spec-patch`, which will be useful for mergify. see: scala-steward-org/scala-steward#2523 scala-steward-org/scala-steward-action#387
Takes a stab at #1471 to make the PR/MR labels appear not only in the textual description, but also using the git hoster's native labelling feature. Implemented for GitHub and GitLab, Bitbucket doesn't have a native label feature, only a plugin (for which support could be added later, now the implementation just logs a warning). It's opt-in for now as it's a change in behaviour not every user might appreciate, but could be promoted to a default later on.
Note: GitHub creates the labels with a standard grey colour (first screenshot), but the user can update that (see second).
PS: Scala Steward is not only a great help, but also a very nice codebase to work with, thank you!
Closes #1471