github
Added get_issue_events , get_issue_timeline and get_issue_event tools
Implements 3 tools dealing with issue events and timeline:
- get_issue_events - all events for the issue https://docs.github.com/en/rest/issues/events?apiVersion=2022-11-28#list-issue-events-for-a-repository
- get_issue_timeline - issue events timeline https://docs.github.com/en/rest/issues/timeline
- get_issue_event - issue event details https://docs.github.com/en/rest/issues/events?apiVersion=2022-11-28#get-an-issue-event
@artemsaveliev as an update, I have been experimenting - and I have played with tool descriptions and things, and it works for the basic cases, but for more complex cases the models do tend to get stuck and then just keep repeating the same requests ad-infinitum!
@SamMorrowDrums The getting-stuck-in-a-loop, and more importantly running out of time/context window is more specific to VSCode Agent implementation - it does not work great with large amounts of data.
Specifically, to me the most interesting use case that the timeline tool covers is discovering cross-reference timeline events - this will allow agent to traverse entire set of issues, as long as they contain links to each other. https://docs.github.com/en/rest/using-the-rest-api/issue-event-types?apiVersion=2022-11-28#cross-referenced In my testing, the agent gave up after about a minute of navigating links - but again, this is specific to VSCode agent implementation. Other agents, especially the ones that have larger context and/or implementation of "memory", should be able to navigate better.
Update: There is a setting in vscode chat.agent.maxRequests that controls how long agent can spend querying tools - by default it's 25. Increasing this number lets agent run in loop for potentially very long time, so it can take advantage of all cross-references between issues and navigate them, for example.
Update - issues tracking this:
