Following #1590, tags work in the Branch field. Two cosmetic improvements would help:

1. Misleading error in task logs. When the ref is a tag, the task log prints fatal: Not a valid object name origin/<tag-name> (Semaphore tries origin/<ref> first, which only works for branches). It falls back to a fresh clone and proceeds correctly, but the fatal: line worries operators reading the log.
2. 'Branch' field/label. The Repository edit dialog labels the field 'Branch' with no hint that tags (or any git ref) are accepted. A tooltip or relabel to 'Branch / Tag' would prevent users from inventing parallel 'release branch' workflows when a tag would suffice.

Both are non-blocking — feature works as-is — but would make tag-based release pinning a first-class workflow.