Closes:#728

Overview

This PR significantly improves how we handle refs in theget_file_contents tool, after usersreported the tool being often broken from bad ref handling.

The problem

Despite the tool description, models can pass as argument to the tool aref formatted either as fully qualified (e.g.refs/heads/beanch_name) or as short user-friendly names (e.g.branch_name).

Theget_repository_content endpoint from the Github API is able to handle both flexibly:

However, theget_reference endpoint doesn't (it requires aref formatted in a specific way):

Our previous logic would fail often because it uses both endpoints but it was not handling user-friendly refs (e.g.branch_name,heads/branch_name,tag_name), which are often provided by models to the tool. This would thus break the tool.

The Solution

This PR introduces new, robust logic to resolve aref by identifying the format in which it was provided and constructing a fully qualifiedref accordingly. In short, the newresolveGitReference function now handles:

• Fully-Qualified refs:refs/heads/main
• Partially-Qualified refs:heads/main
• Short Name refs:main (discovering automatically if it's a branch or a tag)

This ensures that the tool can handle the most common ways in which theref input is provided by the user.

Additionally, I added:

• Comprehensive tests that cover all new logic paths.
• I have added quite detailed comments to the function itself to make the resolution logic, which can be tedious, much easier to follow

Demo