During the v0.7.14 release the token lookup found nothing (tea's OAuth login stores no PAT in its config), so the script silently continued with an empty token and failed 30 minutes later at the upload — after the full build.
Fall back to the git credential store (the access token stored by every git push; Gitea accepts it for API auth)
Remove the interactive prompt (useless in unattended runs — silently reads EOF) and error out immediately when no token is found
During the v0.7.14 release the token lookup found nothing (tea's OAuth login stores no PAT in its config), so the script silently continued with an empty token and failed 30 minutes later at the upload — after the full build.
- Fall back to the git credential store (the access token stored by every `git push`; Gitea accepts it for API auth)
- Remove the interactive prompt (useless in unattended runs — silently reads EOF) and error out immediately when no token is found
The token lookup only read PATs from tea's config — with tea's OAuth
login the config has no token, so the script silently continued with an
empty one and failed 30 minutes later at the upload step. Fall back to
the git credential store (the access token stored by every git push,
accepted by Gitea for API auth), and error out immediately when nothing
is found instead of burning a full build.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
During the v0.7.14 release the token lookup found nothing (tea's OAuth login stores no PAT in its config), so the script silently continued with an empty token and failed 30 minutes later at the upload — after the full build.
git push; Gitea accepts it for API auth)