fix: default prototype mode to deployment_target='none'

[eliasecchig]

Summary

• When --prototype is used without --deployment-target, default to none instead of picking the first available target
• Avoids pulling in unnecessary deployment-specific files for minimal/prototype projects

Changes

• Modified deployment target selection logic in create.py to check for prototype mode before falling through to normal target selection
• If --prototype and no explicit -d, sets deployment_target='none' and prints an info message
• Explicit -d flag still takes precedence even in prototype mode

[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 refines the behavior of the create command by introducing a specific default for the deployment target when in prototype mode. The primary goal is to simplify the setup for prototype projects by automatically setting the deployment target to 'none' if not otherwise specified, thereby avoiding the inclusion of irrelevant deployment configurations and improving efficiency for developers working on early-stage or minimal projects.

Highlights

• Prototype Mode Default: When using the --prototype flag without explicitly specifying a --deployment-target, the system will now default the deployment target to 'none'.
• Resource Optimization: This change prevents the pulling of unnecessary deployment-specific files for minimal or prototype projects, streamlining the development process.
• Explicit Target Precedence: An explicitly provided --deployment-target flag will still take precedence, even when in prototype mode, ensuring user intent is respected.

Changelog

• agent_starter_pack/cli/commands/create.py
  • Modified the deployment target selection logic to check for prototype mode before proceeding with standard target selection.
  • Introduced a conditional block to set deployment_target='none' and print an informational message when --prototype is active and no explicit target is provided.

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 correctly implements the desired behavior of defaulting to deployment_target='none' when using prototype mode without an explicit deployment target. The change is well-isolated and follows the project's conventions. I've added one suggestion to refactor a related code block to improve maintainability by reducing a small amount of code duplication.