Skip to content

Add README for the import automation infra#1930

Open
vish-cs wants to merge 1 commit intodatacommonsorg:masterfrom
vish-cs:readme
Open

Add README for the import automation infra#1930
vish-cs wants to merge 1 commit intodatacommonsorg:masterfrom
vish-cs:readme

Conversation

@vish-cs
Copy link
Contributor

@vish-cs vish-cs commented Mar 24, 2026

No description provided.

@gemini-code-assist
Copy link
Contributor

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 significantly refactors the documentation for the import automation infrastructure. The main README now provides a clearer, architectural overview of the system, while specific operational and setup instructions have been relocated to the executor's README. This reorganization aims to improve the clarity and accessibility of information for different user needs, separating high-level understanding from detailed implementation guidance.

Highlights

  • Documentation Restructuring: The primary README for the import automation system has been completely rewritten to provide a high-level architectural overview of the system, focusing on its core components: Import Job (Cloud Batch) and Ingestion Pipeline (Dataflow + Cloud Workflow).
  • Operational Details Relocation: Detailed operational instructions, such as specifying import targets via git commits, importing to the dev graph, scheduling updates, and deployment procedures (including Cloud Build setup), have been moved from the main import-automation/README.md to the import-automation/executor/README.md.
  • Cloud Build Documentation Consolidation: The standalone import-automation/cloudbuild/README.md file has been removed, and its relevant content describing the Cloud Build configuration and its purpose has been integrated into the updated import-automation/executor/README.md.
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.

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 pull request refactors the documentation for the import automation infrastructure. The top-level README now provides a high-level overview, while detailed instructions for triggering imports via git commits have been moved to the executor's README. The changes improve the documentation structure. I've found a few typos and broken links in the new documentation that should be addressed.

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.

1 participant