fix(remote): send named tag refspecs instead of refs/tags/*

[noyobo]

What & why

Fixes #34.

Push with tags sends refs/tags/*:refs/tags/*. libgit2 Remote::push does not expand that glob — it looks up a literal ref named refs/tags/* and fails with class=Invalid (3). git push --tags expands the glob locally first. Single-tag push_tag already uses a named spec and works.

The engine now lists local tags and pushes refs/tags/{name}:refs/tags/{name} next to the branch spec. Force still prefixes only the branch. Regression: push_with_tags_sends_named_tag_refs against a local bare remote.

Screenshots

N/A — engine behavior only.

Checklist

• New engine coverage in tests/git_engine.rs
• push_refspecs unit tests name tags instead of the glob
• No UI / design-token / undo changes
• cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo test (Rust CI)

Made with Cursor

[cheat2001]

Thanks, this is the right fix. libgit2 really does treat the glob as a literal ref, and naming each tag is what git push --tags does under the hood anyway. Green on all three OSes.

One thing before I merge: the repo keeps source files free of comments, doc comments included (CLAUDE.md §6.5). Can you drop the /// line on push_refspecs and put that note into CLAUDE.md instead, next to the remote.rs entry (the line that says "with_tags always pushes")? Bump the Rust integration count in §9 while you're there.

Not for this PR, but worth knowing: we don't set a push_update_reference callback, so a tag the server rejects (a local v1.0 pointing somewhere else than the remote's) still comes back as a plain "Pushed". Sending every tag makes that case more likely. I'll open an issue for it.