3 ms·
The amount of time I have to spend on investigations, to understand the basics of what something ACTUALLY IS, never ceases to amaze me. Having to scrape away bu
by jtrn 1y ago
The amount of time I have to spend on investigations, to understand the basics of what something ACTUALLY IS, never ceases to amaze me. Having to scrape away buzzwords, ill-conceived descriptions, and unnecessary verbose stuff... it's tiresome.
So i THINK this is what it IS:
A GitHub Action that can be included in GitHub workflow YAML files. It executes the Gemini CLI, passing in prompts, repo context, and event data (like issue text or PR diffs) to generate responses or perform actions. In other words: it's a wrapper that installs and runs the Gemini CLI inside GitHub Actions environments.
It can use GitHub's API (via tokens or apps) to read repo data (issues, PRs, code) and write back (e.g., add labels, comments, or code suggestions). It makes calls to standard HTTPS API endpoints for Gemini LLM" (via the CLI's backend interactions with Google's Gemini API)
- mohsen1 1y agoit says "in the chat interface" write this and that. what chat interface?
- fhinkel 1y agoThat description is 100% correct! In this case, the "chat" happens as a comment on an issue or PR addressing @gemini-cli
- bredren 1y agoIf you have it right, there is a brief discussion on semantic linting in this recent interview with Boris Cherny and Catherine Wu on the Latent Space podcast related to AI-assisted CLI behavior here: https://www.youtube.com/watch?v=zDmW5hJPsvQ&t=1760s https://www.youtube.com/watch?v=zDmW5hJPsvQ&t=1760s I've not explored this use of CC yet, anyone actively using AI-assisted CLI in CI/CD? Not automated PR review but either to semantically pass / fail an MR or some other use of terminal-capable, multi-context mashup during CI/CD?