Skip to content

Use autopush API env for import tool#1929

Merged
vish-cs merged 1 commit intodatacommonsorg:masterfrom
vish-cs:resolve
Mar 24, 2026
Merged

Use autopush API env for import tool#1929
vish-cs merged 1 commit intodatacommonsorg:masterfrom
vish-cs:resolve

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 streamlines the configuration of the import tool by defaulting its API environment to 'AUTOPUSH'. This change simplifies the process of connecting to the correct Data Commons API endpoint and ensures that the appropriate API key is used based on the selected environment, improving consistency and reducing manual configuration efforts.

Highlights

  • Default API Environment: The import tool's default API environment has been set to 'AUTOPUSH' through a new configuration parameter dc_api_env.
  • Dynamic API Configuration: The logic for setting the Data Commons API key and root URL has been updated to dynamically select between the production and autopush environments based on the dc_api_env configuration.
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 configuration for the Data Commons API environment. It introduces a dc_api_env configuration to switch between 'AUTOPUSH' and other environments, setting the DC_API_ROOT and DC_API_KEY environment variables accordingly. This is a good simplification.

My review includes one suggestion in main.py to improve the new logic by restoring a check for a non-empty API key, which was present in the previous implementation. This prevents a potential change in behavior for downstream tools and also improves the code's readability by reducing duplication.

@vish-cs vish-cs force-pushed the resolve branch 5 times, most recently from c15079d to 73d5449 Compare March 24, 2026 07:19
@vish-cs vish-cs merged commit 7d329eb into datacommonsorg:master Mar 24, 2026
9 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