Repair a Delete button in a GitHub repo

A developer had Jules fix a broken Delete button, add tests, and leave the branch ready for review.

Done with Geminiยท Intermediate

What they did
They granted Jules access to a GitHub repository, chose the project and branch, and asked it to repair the Delete button. To define the expected behavior, they pointed it at a matching control in another module and said deletes should be blocked once content was more than two hours old. Jules proposed a plan, got the go-ahead, cloned the code, and made the change.
How it went
Jules created the code updates and also wrote test cases that were not requested. The branch appeared in GitHub, and the developer inspected the changes before publishing them to a bug-fix branch. The post does not say how long it took or confirm the fix beyond that.
Tips
A working example in the same codebase can make the requirements much clearer. If the agent is doing several things at once, keep an eye on the review so you can catch any missed details.

Try it yourself with Gemini

In [repo URL or local path], the [feature name] is broken. Use [another module, file, or component] as the model for how it should behave, and make it so [desired behavior, including any time limit or rule]. Start by finding the likely cause and outlining a short plan, then wait for my approval before editing anything. After I approve, make the fix on a new branch, add tests for the new behavior, and pause before any irreversible action such as merging, publishing, deleting, or submitting. Finish by summarizing the changes and flagging anything I should check in [CI / GitHub Actions / a pull request].

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on calvin.my โ†—

2 more reports of this

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.