Switch plugins repository order to pick up skie

[mlykotom]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @mlykotom, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Based on the title, this pull request adjusts the order in which Gradle searches for plugins defined in the pluginManagement block. The change aims to resolve potential issues with plugin resolution, specifically mentioning the 'skie' plugin, by prioritizing mavenCentral() over gradlePluginPortal() in the search order.

Highlights

• Plugin Repository Order: Swapped the order of mavenCentral() and gradlePluginPortal() within the pluginManagement block in settings.gradle.kts.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request modifies the settings.gradle.kts file to change the order of repositories in the pluginManagement block, moving mavenCentral() before gradlePluginPortal(). The stated purpose is to ensure the SKIE plugin is picked up correctly. My review includes one suggestion aimed at improving the maintainability of this change by encouraging documentation of the specific rationale behind this repository ordering directly within the code. As no explicit style guide was provided, this feedback is based on general software engineering principles emphasizing the importance of documenting configurations whose necessity might not be immediately obvious to future maintainers.

[gemini-code-assist]

The reordering of plugin repositories is a key change. The PR title mentions this is "to pick up skie". To ensure long-term maintainability and clarity for other developers, it's highly recommended to add a brief comment explaining why this specific order (mavenCentral() before gradlePluginPortal()) is necessary for the SKIE plugin. For instance, does it resolve a version conflict, or ensure a specific artifact is pulled from mavenCentral? This context directly in the code is invaluable.

        // NOTE: This repository order is crucial for SKIE plugin resolution.
        // Please add a brief explanation below, e.g.:
        // "Needed because [specific SKIE dependency/conflict details]"
        mavenCentral()
        gradlePluginPortal()