tea login add creates token without scopes #542
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#542
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After executing
tea login add
with username and password, the token created does not have any scopes and all commands are useless.Currently, I am creating a token with scopes manually via user settings.
I used
curl
as a workaround to create token and use it withtea login add
.Once gitea/go-sdk#616 or gitea/go-sdk#617 are merged I will send a PR here to resolve this.
Thanks for reporting!
Curious where this stands. I'm running into this issue with a CI pipeline I'm developing, and it would be helpful for #546 to be merged. It looks like gitea/go-sdk#617 is merged.
It looks like #616 did not get merged and it's still an issue for me. It created a token and then complained that it didn't have enough scopes defined and errored out. I had to create the token manually and pass it to
tea login
.