Tea-Cli

mirror of https://gitea.com/gitea/tea.git synced 2026-07-31 19:46:35 +00:00

Files

T

Zach Winter 73b6bf3e23 fix(context): clarify the fallback login prompt wording (#1061 )

The prompt shown when no login matches the current repository reads:

```
NOTE: no gitea login detected, whether falling back to login 'X'?
```

Two problems, both raised by @magistra-aria in #817:

- **"whether"** is a conjunction that needs two stated alternatives, so it doesn't parse in front of a yes/no confirm.
- **"no gitea login detected"** is misleading. The condition is that no *configured login matched this repository's remote* — not that a Gitea instance is missing. Read literally it suggests the CLI expects gitea.com specifically, which is how at least one user (me) first misread it.

Reworded to say what actually happened, for both the interactive prompt and its non-interactive counterpart:

```
NOTE: no login matched this repository. Fall back to login 'X'?
```

Strings only, no logic change.

Refs #817

---------

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Zach Winter <contact@zachwinter.com>
Reviewed-on: https://gitea.com/gitea/tea/pulls/1061
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Zach Winter <222839+zachwinter@noreply.gitea.com>

2026-07-26 01:38:10 +00:00

api

fix(http): add transport timeouts so tea fails fast on stalled servers (#1020 )

2026-06-26 19:59:05 +00:00

auth

fix(http): add transport timeouts so tea fails fast on stalled servers (#1020 )

2026-06-26 19:59:05 +00:00

config

upgrade go sdk and add test (#1048 )

2026-07-01 18:06:19 +00:00

context

fix(context): clarify the fallback login prompt wording (#1061 )