Skip to content

Update and move nightly builds link in README#2220

Merged
robfrank merged 1 commit intoArcadeData:mainfrom
gramian:main
May 25, 2025
Merged

Update and move nightly builds link in README#2220
robfrank merged 1 commit intoArcadeData:mainfrom
gramian:main

Conversation

@gramian
Copy link
Collaborator

@gramian gramian commented May 22, 2025

What does this PR do?

The link for the nightly builds in the README is updated and moved to the more suitable Releases section.

Related issues

#2197

Checklist

  • I have run the build using mvn clean package command
  • My unit tests cover both failure and success scenarios

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @gramian, I'm Gemini Code Assist1! 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!

Summary of Changes

As gemini-code-assist, I've reviewed this pull request. The main objective of this PR is to improve the README.md file by updating the link to the nightly builds and moving it to a more logical location within the document. Specifically, the old link is removed, and the new, correct link is added near the section describing the different release variants.

Highlights

  • Relocate Link in README: The updated nightly builds link has been moved from its previous position (near the contribution guide) to a new location within the 'Releases' section of the README.md file, specifically after the description of the release variants.

Changelog

  • README.md
    • Removed the old nightly builds link around line 148.
    • Added the new nightly builds link around line 118, placing it after the list of release variants.
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.


A link was old and wrong,
Moved it where it should belong,
Docs now clear and bright,
Guiding users right,
Singing a happy song.

Footnotes

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

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR effectively updates the nightly builds link and relocates it to a more appropriate section in the README.md file. The changes are clear, the new link is correct as per the referenced issue #2197, and the new placement under the 'Releases' section is more logical. Good job on this improvement!

Merge Readiness

The changes in this PR are accurate and improve the README's clarity and correctness. From the perspective of the content changes in README.md, this pull request appears ready for merging.

As a general reminder, please ensure any repository-specific checklist items (such as the build and test confirmations mentioned in the PR description) are addressed according to your team's process before finalizing the merge. I am not authorized to approve pull requests; this review is for feedback purposes, and the PR should undergo any further necessary reviews or checks as per your contribution guidelines.

@robfrank robfrank merged commit ff822f7 into ArcadeData:main May 25, 2025
7 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants