beyerjsb

> Can you report the output of `git remote -v` after running, and the git-filter-repo command line you used? ``` PS > git remote -v origin (fetch) origin (push) ```...

No, I'm not using --partial, I'm not afraid of a complete rewrite (it will be anyway), and I'm also replacing in-situ, not using --source or --target. Also I'm always going...

I did some testing, and the culprit is --mirror when cloning. When I clone "normally", gilter filter-repo removes the remote. I'll update the title and the text accordingly.

I have currently no stakes in this topic anymore, but for the sake of completeness I want to mention: - https://community.tyk.io/t/tyk-gateway-virtual-endpoint-request-headers-vs-response-headers-inconsistency/3221/6 - https://github.com/TykTechnologies/tyk/issues/1514 In my eyes this is a critical/blocker...

I wanted/needed this myself, but after some pondering, I realized that my knowledge about how post-receive-hooks in Git work, blinded me about the ways Gitea does work. You don't have...

How about Gitea provides just a toggle (yes/no) for the Gitea Webhook if the payload should be sent or not. Very simple, quick change. Would help in this case.

> How about use https://github.com/jenkinsci/gitea-plugin directly? This is not the same. Using the API the Jenkins Git plugin provides, it triggers the *polling* of the repos, and takes polling options...