-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Document the GithubAgent Feature #1291
Comments
ACK, on it! |
@laz-001 Hey! That would be interesting, we are still evaluating if this is a true need people have or more of a good to have. Would love to know how you would go about using it |
🔄 Documentation Update: Created GithubAgent feature documentation
The documentation provides a starting point for understanding this feature and can be expanded as more information becomes available. |
i would create an github account, assign it to the bot. within a solo project, the agent can assist me to overcome "the first step barriers". I file issues, agent creates a draft (or even final) PR, i go on and correct/complement. far better that filing issues/prs alone. |
In a project with the first alpha/beta testers, this gets more interesting. users file issues and get quick first feedback. solo-dev (poor me) has reduced workload to identify bug-locations etc. (at minimum). |
/agent take a look at info within #1291 (comment). Your document needs to become more compact, write mostly what you know, without much theoretizing. |
Idea
fascinated by this agent (theskcd) the runs around in this repo.
my (paid) AIDE IDE Agent says
maybe document what the agent here on the AIDE repo is about, if there's a relation to AIDE-IDE agents.
My question: how can i obtain an own instance of an in-repo agent?
The text was updated successfully, but these errors were encountered: