build: update README for deprecation notice

[sofisl]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

Description

Please provide a detailed description for the change.
As much as possible, please try to keep changes separate by purpose. For example, try not to make a one-line bug fix in a feature request, or add an irrelevant README change to a bug fix.

Impact

What's the impact of this change?

Testing

Have you added unit and integration tests if necessary?
Were any tests changed? Are any breaking changes necessary?

Additional Information

Any additional details that we should be aware of?

Checklist

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease
• Appropriate docs were updated
• Appropriate comments were added, particularly in complex areas or places that require background
• No new warnings or issues will be generated from this change

Fixes #issue_number_goes_here 🦕

[generated-files-bot]

Warning: This pull request is touching the following templated files:

• README.md - README.md is managed by synthtool. However, a partials file can be used to update the README, e.g.: https://github.com/googleapis/nodejs-storage/blob/main/.readme-partials.yaml

[gemini-code-assist]

Summary of Changes

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

This pull request primarily focuses on updating the project's documentation to reflect its deprecation and migration to a new repository. Concurrently, it modernizes and simplifies the automated build configuration by adopting a more abstract and maintainable approach for OwlBot, reducing boilerplate and improving clarity.

Highlights

• README Deprecation Notice: A prominent deprecation notice has been added to the README.md file, directing users to the new GOOGLE-CLOUD-NODE repository where the project's content and history have been moved.
• OwlBot Configuration Simplification: The owlbot.py script has been significantly refactored, replacing extensive manual file copying and template handling logic with a single, streamlined call to node.owlbot_main. This simplifies the build process and leverages higher-level abstractions.
• Copyright Year Update: The copyright year in owlbot.py has been updated from 2021 to 2022.

Changelog

• README.md
  • Added a deprecation notice at the top of the file.
  • Included a link to the new GOOGLE-CLOUD-NODE repository.
• owlbot.py
  • Updated the copyright year from 2021 to 2022.
  • Refactored the script to use node.owlbot_main for simplified OwlBot processing.
  • Removed extensive manual file copying, exclusion logic, and template handling.
  • Removed imports for synthtool, synthtool.gcp, logging, pathlib, _tracked_paths, shell, and shutil due to the refactoring.

Activity

• The pull request description is a standard template, indicating no specific human activity or comments have been recorded yet.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds a deprecation notice to the README.md file and simplifies the owlbot.py script. The simplification of the build script is a good improvement. However, there's a minor formatting issue in the deprecation notice in the README that should be corrected.