Feature request for product/service
Cursor IDE
Describe the request
Many workflows use annotated git tags (e.g. v1.2.3) to drive automated releases, such as GitHub Actions triggered on push to refs/tags/v*. From the CLI, this works well: pnpm version patch (or npm version) creates a tag, and a plain git push with push.followTags=true (or git push origin main --follow-tags) pushes both the branch and its tags, triggering the release pipeline.
The Source Control “Publish Branch” / “Push” action in Cursor/VS Code appears to use an explicit refspec like git push origin HEAD:refs/heads/main. That form of push ignores the push.followTags git config and does not send tags, leaving local tags that never reach the remote. As a result, tag-based workflows do not run, even though git is configured to follow tags.
The requested feature is to change the behavior of “Publish Branch” so that it either (a) respects the git config (i.e. uses default push behavior that honors push.followTags), or (b) respects an explicit setting to always include --follow-tags on pushes initiated from Source Control. This would allow tag-driven release automation to work seamlessly when using the built-in UI, without requiring additional manual tag pushes from the terminal.