Conversation
Using Gemini Code AssistThe 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 by creating a comment using either
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 Limitations & Feedback Gemini Code Assist 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
702a84d to
0e14638
Compare
| // firebase-appdistribution-gradle/src/prodTest/java/com/google/firebase/appdistribution/gradle/BeePlusGradleProject.java#L59-L60 | ||
| private const val LATEST_GRADLE_VERSION = "9.4.0" | ||
| private const val LATEST_AGP_VERSION = "9.2.0-alpha02" | ||
| private const val LATEST_GRADLE_VERSION = "9.5.0-milestone-5" |
There was a problem hiding this comment.
traditionally, we've never tested "milestone" versions of Gradle itself. Only release candidates and regular versions.
I think it makes sense to maintain that. To accomplish this, we will probably need to filter AGP versions to only "rc", too - and ignore any "alpha" versions.
What do you think?
No description provided.