stefanvodita commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2918941880
Linking the PR related to the question above: #14721.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
dweiss commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2910623550
I have a question - I have a fork of Lucene and create a pull request
against that fork (not against the primary repo). This labeler action then
fails because it - for some reason - lacks
stefanvodita commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2636455151
I've seen new PRs get labels assigned. I like how it's working!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
pseudo-nymous commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629515885
I'll be happy to work on these. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
stefanvodita commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629513783
Brilliant! Let us know if you find anything. If you're interesting in this
area of GitHub workflows / community tools, there are a few others that would
be great to do:
1. #13898
pseudo-nymous commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629507768
Thanks.
I checked if same script could be used to label older PRs but there is no
such event corresponding to already closed PR.
Maybe we can write an individual script
stefanvodita commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629498867
Thank you for this contribution @pseudo-nymous, I merged it just now and I'm
really looking forward to see the first PR using it!
--
This is an automated message from the Apache G
stefanvodita merged PR #14101:
URL: https://github.com/apache/lucene/pull/14101
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucen
mikemccand commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2624467638
Wow, this looks really awesome! I wish we could retroactively apply it to
PRs missing their module labels ... but let's start with this change (so new
PRs are labeled).
--
This is
pseudo-nymous commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935416351
##
.github/labeler.yml:
##
@@ -0,0 +1,134 @@
+# This file defines module label mappings for the Lucene project.
+# Each module is associated with a set of file g
pseudo-nymous commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935253167
##
.github/labeler.yml:
##
@@ -0,0 +1,134 @@
+# This file defines module label mappings for the Lucene project.
+# Each module is associated with a set of file g
stefanvodita commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935220020
##
.github/labeler.yml:
##
@@ -0,0 +1,134 @@
+# This file defines module label mappings for the Lucene project.
+# Each module is associated with a set of file gl
pseudo-nymous commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2623844525
> This is great @pseudo-nymous! I left minor comments that I would like to
see addressed, but this is very good already. I retract my concern about the
action budget. This is runni
pseudo-nymous commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2623829618
Did further testing with new sync flag, change is working as expected.
Ref: https://github.com/pseudo-nymous/lucene/pull/3
--
This is an automated message from the Apache Git S
pseudo-nymous commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935132629
##
.github/workflows/label-pull-request.yml:
##
@@ -0,0 +1,21 @@
+# This file defines the workflow for labeling pull requests with module tags
based on the chan
pseudo-nymous commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935130586
##
.github/labeler.yml:
##
@@ -0,0 +1,134 @@
+# This file defines module label mappings for the Lucene project.
+# Each module is associated with a set of file g
pseudo-nymous commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1935129051
##
.github/labeler.yml:
##
@@ -0,0 +1,134 @@
+# This file defines module label mappings for the Lucene project.
+# Each module is associated with a set of file g
stefanvodita commented on code in PR #14101:
URL: https://github.com/apache/lucene/pull/14101#discussion_r1934819611
##
.github/workflows/label-pull-request.yml:
##
@@ -0,0 +1,21 @@
+# This file defines the workflow for labeling pull requests with module tags
based on the chang
stefanvodita commented on PR #14101:
URL: https://github.com/apache/lucene/pull/14101#issuecomment-2622114022
@pseudo-nymous, I'm only seeing this now, sorry! At first glance, it matches
what I had in mind - thank you for addressing that issue! I'll do an in-depth
review soon, but I'd appre
pseudo-nymous opened a new pull request, #14101:
URL: https://github.com/apache/lucene/pull/14101
### Description
Adds a new bot to automate labelling of pull requests based file changes on
the module.
This bot uses `.github/labeler.yml` file to maintain mapping for module tags
to cor
20 matches
Mail list logo
