Conversation
Using Gemini Code AssistThe 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
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 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. |
| setup_command: | | ||
| scripts/setup_bundler.sh | ||
| scripts/install_prereqs.sh WatchOSSample watchOS | ||
| # Note: The original job had a condition `([ -z "$plist_secret" ] || scripts/build.sh WatchOSSample watchOS)`. The _build.yml workflow's `check_secrets` job already handles the logic of skipping on forks if secrets are present, so no explicit plist_secret is needed here in the `with` section unless used in the setup_command. |
There was a problem hiding this comment.
| # Note: The original job had a condition `([ -z "$plist_secret" ] || scripts/build.sh WatchOSSample watchOS)`. The _build.yml workflow's `check_secrets` job already handles the logic of skipping on forks if secrets are present, so no explicit plist_secret is needed here in the `with` section unless used in the setup_command. |
Reducing the amount of locations that I'll need to configure Xcode versions.
#no-changelog