create repo wont work #353
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#353
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?
Hello,
I have been using tea for some time and built myself a script to upload to gitea. This ran for a long time without any problems. Currently I get the following error:
unfortunately i can't find the error. i haven't changed anything in the script for a long time.
Gitea Version: 1.15.0+dev-65-g0bb8bd819
Tea Version: 0.7
Kind regards
Thanks for reporting.
I can't reproduce with tea 0.7 + gitea 1.14.0-rc2 or 1.15.0+dev-21-gf4e677edb (current gitea.com) or 1.15.0+dev-84-g0d1a5e0ff (current try.gitea.io).
Did it work for you before with tea 0.7? In that case this is an upstream bug in gitea..
Hello, unfortunately I have only just got around to replying to the email. I use Gitea as a Docker image from here https://hub.docker.com/r/gitea/gitea with the tag :latest. In the "beginning" this worked with Tea. I think it was last autumn - at some point it didn't work anymore. I know that's not meaningful ;-) I didn't think about it either. Now I wanted to adapt my script and use it with the current version 0.7. Now it no longer works. It also doesn't work with the old version 0.4.
closing, as I still can't reproduce. If the problem comes up again with a recent tea version feel free to re-open :)