pseudo-nymous commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2735279420
@stefanvodita I have added a fix for it. Please take a look.
https://github.com/apache/lucene/pull/14369
--
This is an automated message from the Apache Git Service.
To res
stefanvodita commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2733970610
Just to clarify - the restriction @dweiss mentioned applies to the
`changelog-enforcer` action, but not to the `checkout` action we are using.
@pseudo-nymous - I'm seeing
dweiss commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2726850239
> dangoslen/changelog-enforcer@v3 is not allowed to be used in apache/lucene
Apache projects are not allowed to use arbitrary actions for security
reasons, please take a look a
pseudo-nymous commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2726787800
Thanks @stefanvodita! I will take a look at the fix and propose changes
accordingly.
--
This is an automated message from the Apache Git Service.
To respond to the message,
stefanvodita commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2721556890
@pseudo-nymous, I've attempted a fix in #14355.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
pseudo-nymous commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2693761988
Thanks for updating the script with PR number. I'll root cause and fix the
issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, p
stefanvodita commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2692956304
I was looking at the workflow that @pseudo-nymous wrote. The
[logs](https://github.com/apache/lucene/actions/runs/13597403773/job/38017259510)
for #14276 say there is no CHANGE
stefanvodita closed issue #13898: Create a bot to check if there is a CHANGES
entry for new PRs
URL: https://github.com/apache/lucene/issues/13898
--
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
stefanvodita commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2411705472
@prudhvigodithi - I opened #13898 inspired by your PR, tested it on my fork,
and it's working correctly.
@javanna - I like that idea! Maybe we can do that as a follow-up.
javanna commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2410385807
Yes to this! It would be great to combine this with setting the milestone :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
prudhvigodithi commented on issue #13898:
URL: https://github.com/apache/lucene/issues/13898#issuecomment-2408659537
Here is the sample PR with change-log verifier action added
https://github.com/prudhvigodithi/lucene/pull/1, we can add the same workflow
to lucene repo. But I see the error
11 matches
Mail list logo