Skip to content
This repository was archived by the owner on Mar 16, 2026. It is now read-only.

build: update README to indicate that source has moved#1308

Merged
chalmerlowe merged 1 commit intomainfrom
update-readme-post-migration
Mar 16, 2026
Merged

build: update README to indicate that source has moved#1308
chalmerlowe merged 1 commit intomainfrom
update-readme-post-migration

Conversation

@chalmerlowe
Copy link
Contributor

@chalmerlowe chalmerlowe requested review from a team as code owners March 16, 2026 13:08
@product-auto-label product-auto-label bot added the size: xs Pull request size is extra small. label Mar 16, 2026
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/python-bigquery-sqlalchemy API. label Mar 16, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello, 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!

This pull request updates the README.rst file to clearly inform users that the repository has been archived and its contents migrated to a new location. This ensures that anyone visiting the old repository is immediately directed to the active development branch, improving discoverability and reducing confusion for contributors and users.

Highlights

  • Repository Archival Notification: A prominent note has been added to the README.rst file, informing users that this GitHub repository is archived and its contents have been moved to the google-cloud-python monorepo.
  • Link to New Location: The note includes a direct link to the new location of the sqlalchemy-bigquery package within the google-cloud-python repository, specifically pointing to the tree/main/packages/sqlalchemy-bigquery path.
Changelog
  • README.rst
    • Added a prominent note at the top of the file about the repository's archival and its new location.
Activity
  • No specific activity (comments, reviews, etc.) was provided in the context for this pull request.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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.

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 configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@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

The pull request effectively updates the README.rst file to inform users about the archiving of the repository and the new location of its contents. This is a crucial update for user guidance. The changes are clear and directly address the stated objective.

@@ -1,3 +1,8 @@
:**NOTE**: **This github repository is archived. The repository contents and history have moved to** `google-cloud-python`_.

Choose a reason for hiding this comment

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

medium

The leading colon : before **NOTE** is not standard reStructuredText syntax and might cause unexpected rendering or parsing issues. It's best to remove it for proper formatting and adherence to reStructuredText conventions.

Suggested change
:**NOTE**: **This github repository is archived. The repository contents and history have moved to** `google-cloud-python`_.
**NOTE**: **This github repository is archived. The repository contents and history have moved to** `google-cloud-python`_.

@chalmerlowe chalmerlowe added the automerge Merge the pull request once unit tests and other checks pass. label Mar 16, 2026
@chalmerlowe chalmerlowe merged commit e6e17c2 into main Mar 16, 2026
13 of 15 checks passed
@chalmerlowe chalmerlowe deleted the update-readme-post-migration branch March 16, 2026 17:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: bigquery Issues related to the googleapis/python-bigquery-sqlalchemy API. automerge Merge the pull request once unit tests and other checks pass. size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants