This sounds like Gemini Code Assist rebranded under the successful Gemini CLI banner. I'm sure this was done to "consolidate" offerings and brands, but this is just way more confusing. CLI has a meaning, and this doesn't seem to have a CLI at all? Product looks cool, but the naming is just baffling
Gemini CLI GitHub Actions
51–60 of 100 posts
Re: Gemini CLI GitHub Actions
#52Wait, is this CLI or is this a github action or is this a github application? Also, I thought Jules was the "coding agent" they are working on. Now this is taking it over or is this like another case of Google self-competing? Someone needs to take charge at this company with a strong vision, because they are all over the place and spreading themselves thin, which in turn spreads thin the customer/brand equity. At thi…
They need a boundary between their research culture and their software culture. One org, two cultures. The chaos you describe is actually a significant positive in research environments. It's not spreading oneself thin, it is diversifying and decorrelating ones' efforts. You can't centrally plan all innovation. But for the interface between the customer and the research output, which is a software and product problem…
Completely agree - the research output should be integrated into a customer facing product, instead they are trying to integrate customers into into research output.
Re: Gemini CLI GitHub Actions
#53Wait, is this CLI or is this a github action or is this a github application? Also, I thought Jules was the "coding agent" they are working on. Now this is taking it over or is this like another case of Google self-competing? Someone needs to take charge at this company with a strong vision, because they are all over the place and spreading themselves thin, which in turn spreads thin the customer/brand equity. At thi…
[deleted]
Re: Gemini CLI GitHub Actions
#54The 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…
it says "in the chat interface" write this and that. what chat interface?
That description is 100% correct!
In this case, the "chat" happens as a comment on an issue or PR addressing @gemini-cli
Re: Gemini CLI GitHub Actions
#55I tried this out last month. It was useful to summarize big PR's, and even found minor issues. But nothing really useful for professionals, only for overworked open source maintainers to review and feedback newbies.
Re: Gemini CLI GitHub Actions
#56[dead]
Re: Gemini CLI GitHub Actions
#57Earlier quoted context omitted.
Jules works in a VM, asynchronously, on a separate checkout of the code. Gemini CLI works synchronously with the user (unless you YOLO) and in your own directory on your own machine on your own checkout. Two different modalities.
And Gemini CLI github action (this project) runs again in a VM (github action runner) on a separate checkout of the code. This is what OP meant with multiple coding agents.
[deleted]
Re: Gemini CLI GitHub Actions
#58Last year, I was actually working on a bounty platform for Github PR's.
The low quality human-authored PR's that came in (due to the incentive we offered) combined with the fact that a draft PR could be made for pennies with AI made this concept dead in the water as far as I'm concerned.
The pain point of getting some attention and action on your opensource codebase is really no longer relevant, in fact the pain point seems to be moving to how to optimize the limited reviewer / maintainer bandwidth under the onslaught of proposed suggestions.
To this end I've been experimenting with a framework that builds PR's from the major agents and but with a focus on how to structure the tasks and review process that optimize the review => accept/revise cycle. If you're interested I've been writing up some case studies here: https://github.com/sutt/agro/blob/master/docs/case-studies/a...
Re: Gemini CLI GitHub Actions
#59> 7. Google One and Ultra plans, Gemini for Workspace plans These plans currently apply only to the use of Gemini web-based products provided by Google-based experiences (for example, the Gemini web app or the Flow video editor). These plans do not apply to the API usage which powers the Gemini CLI. Supporting these plans is under active consideration for future support. Again, with the complicated subscription. Plea…
I'm honestly a bit confused by the free tier of Gemini. I've been using it with different agents (Aider, and then Crush), and I hit the rate limits FAST. Like, after maybe 5 or 6 requests it just blows up. Then I can try again quite a few times, and it hits the limit. Then eventually I guess I hit my daily limit and it just stops working until the next day. I mean this has been enough to get my feet wet and have some…
I added a key rotator to my AI coder, and asked a couple of friends to make keys for me. That helped code a good chunk of http://typedai.dev when 2.5 Pro came out
Re: Gemini CLI GitHub Actions
#60Earlier quoted context omitted.
If I didn't know better, I'd think you were joking.
To be fair, the "Hello Vasco" is a generated background image and not part of the chat context. But still, you would think they would put your name in the system prompt.
> you would think they would put your name in the system prompt
They probably do, along with "pretend to not have any personal information about the user".