googleapis / googleapis/librarian
all: create a GitHub bot account to enable Gemini CLI–driven PRs via GitHub Actions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 45
- Forks
- 62
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 175
Description
We can’t create PRs with Gemini CLI today without a bot identity. I’ve been playing around with https://github.com/google-github-actions/run-gemini-cli to create issues and PRs, and we need to create and set up a robot account (that has signed the CLA) in order to enable PR creation.
Example: https://github.com/googleapis/librarian/pull/4675
we should create a librarian-bot account and use it for Gemini CLI–driven PRs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing google-github-actions/run-gemini-cli and the example pull request googleapis/librarian#4675. Then locate the repository’s GitHub Actions configuration and determine how the proposed librarian-bot identity would be used. Done means the bot account exists, has signed the CLA, and Gemini CLI-driven pull requests can be created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100