Login to docker to fix workflow #526
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#526
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix-test-workflow"
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?
Same as for the release workflow.
blocking this as it opens up secrets to PRs
Good catch.
I see two solutions:
I'd favor (1). Your opinion?
@techknowlogick I've used a personal read-only public token of my own Docker account now to move forward. If you have time, it would be great to add a token from the Gitea docker org. Public read-only tokens should only have a use case for rate limiting AFAICS.
@pat-s I've created some temporary RO tokens
DOCKER_RO_USERNAME
andDOCKER_RO_PASSWORD
under my personal username, as I'm having some trouble getting into the giteabot docker hub account. Once I get access, I'll be able to update them :)Thanks! Though this wouldn't have been needed as my last comment tried to communicate I already did the same with
DOCKER_USERNAME_PUBLIC
😄For now, I only need an approval here to move forward. I want to get the renovate updates auto-merged again.