Hey
We have already renovate config. No need to have single/common Gradle
file. We can define paths in the configuration:
https://github.com/apache/polaris-tools/blob/main/.github/renovate.json5
I created https://github.com/apache/polaris-tools/pull/7 about CODEOWNERS.
Regards
JB
On Thu, Apr 1
Yes it could be useful too. Would it require all projects inside
polaris-tools to be managed with a common Gradle build file?
--
Pierre
On Wed, Apr 16, 2025 at 7:29 PM Jean-Baptiste Onofré
wrote:
> By the way, do you also want other resources (like renovate config) ?
>
> I guess not, but wan
By the way, do you also want other resources (like renovate config) ?
I guess not, but wanted to double check.
Regards
JB
On Wed, Apr 16, 2025 at 6:31 PM Pierre Laporte wrote:
>
> Hi folks
>
> I am going to open a few PR against the polaris-tools repository to improve
> benchmarks, especially r
Hi,
The LDAP group is the same.
What's missing on polaris-tools is the .github/CODEOWNERS (used to
auto assign reviewers).
I will add it.
Regards
JB
On Wed, Apr 16, 2025 at 6:31 PM Pierre Laporte wrote:
>
> Hi folks
>
> I am going to open a few PR against the polaris-tools repository to improv
Hi folks
I am going to open a few PR against the polaris-tools repository to improve
benchmarks, especially regarding update-related workloads. I opened a new
PR but noticed that, unlike with the PR against `apache/polaris`, nobody is
automatically added as reviewer when a pull request is created
