mikemccand commented on issue #14190:
URL: https://github.com/apache/lucene/issues/14190#issuecomment-2630817713
It might in theory check the `lucene/CHANGES.txt` to look for an entry (with
the PR/issue number) summarizing the PR? Then it could see which Lucene
release the issue is under.
This would also serve to validate that `CHANGES.txt` was updated (we also
often forget this). But ... many PRs are trivial and don't require a
`CHANGES.txt` entry, so I guess we'd need some escape hatch to tell the bot
it's OK.
--
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...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
