add .env.example for environment configuration

[ChaitanyaChute]

Solves issue #18
Summary
This PR adds a .env.example file to document all required environment variables for the project.
It improves onboarding for new contributors and reduces confusion during local setup by providing a clear template they can copy into their own .env file.

Details
Added a new .env.example file in the project root.
Included placeholder environment variables based on what the CLI currently expects.
No functional changes to the codebase—this is strictly a developer-experience improvement.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @ChaitanyaChute, 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 significantly improves the developer experience by adding a ".env.example" file. This new file serves as a clear template for environment variables, streamlining the local setup process for new contributors and ensuring consistent configuration across development environments without altering any core functionality.

Highlights

• Environment Configuration Documentation: Introduces a ".env.example" file to clearly document all necessary environment variables for the project.
• Developer Onboarding Improvement: Enhances the onboarding process for new contributors by providing a template that simplifies local setup and reduces potential confusion.
• No Functional Code Changes: This pull request is solely focused on improving developer experience and does not introduce any functional changes to the existing codebase.

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 introduces a .env.example file to document the necessary environment variables, which is a great step towards improving the developer onboarding experience. The change is straightforward and adds the GEMINI_API_KEY. I've suggested a small improvement to make the file even more helpful by refining the comment with a direct link and ensuring the file ends with a newline, which is a common convention.