Add git rev-parse completions

[rasitakyol]

Warp issue warpdotdev/warp#12319 requests revision completions for git rev-parse. Today, comparable Git commands can suggest refs, but git rev-parse has no command-signatures metadata for its revision arguments.

The command-signatures package should add a git rev-parse signature that suggests local branches, remote branches, commits, and tags while preserving the existing handwritten git.json structure.

An implementation is available in #291, including package presubmit coverage and end-to-end verification in a local Warp build.

[oz-for-oss]

@rasitakyol

Here's what I found while triaging this issue:

Current code confirms git rev-parse does not have completion metadata yet. An open implementation in #291 appears to add the requested revision completions.

Maintainer details

I concluded that add completion metadata for git rev-parse so revision arguments suggest branches, commits, and tags..

Triage summary

This is an actionable enhancement request for Git command completions. The current handwritten git.json spec has comparable revision-aware arguments for commands such as git show, git log, and git reset, but it does not define git rev-parse, so there is no metadata path for Warp to suggest refs for that command.

Likely implementation scope is limited to adding a rev-parse subcommand entry in command-signatures/json/git.json that uses the existing Git generators for local branches, remote branches, commits, and tags. The referenced PR #291 appears to implement exactly that single-file change and includes presubmit plus local Warp verification.

Duplicate scan: I checked all open non-PR issues and recently closed issues allowed by the dedupe workflow. The closest open Git-related request is #287 for git update-ref, but it targets a different Git subcommand and argument shape, so this issue is not a duplicate.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.