silverwind

It does seem like a useful rule to me.

An extension to this request is to support web links to clone a git repo directly into the editor as a new project. VS Code supports such a scheme: ```...

Is it using `./contrib/backport`? When I try that, it fails: ```sh $ go run ./contrib/backport --version v1.21 --no-push 27503 * Backporting 27503 to origin/release/v1.21 as backport-27503-v1.21 * `git fetch origin...

https://github.com/go-gitea/gitea/pull/27501 was also clean cherry-pick which I backported with this bash script now.

Contributed the script in https://github.com/go-gitea/gitea/pull/27519.

Why does the log not show any error?

Maybe this `if` branch should log or throw the error? https://github.com/GiteaBot/gitea-backporter/blob/aab91a4ce0781253c735e2cfa83472f8afe8ab2d/src/git.ts#L78-L84 I would make it throw an error on any command failure, much better than returning `false` and not knowing...

Overall I think the bot should make use of https://github.com/go-gitea/gitea/tree/main/contrib/backport, so that the backporting mechanism can be tested locally in the repo as well. Likely that script needs a few...

After https://github.com/go-gitea/gitea/pull/27520, we could make the backporter use this script to cherry-pick. Imho, is is much better to having something that can be ran and debugged locally and we will...

https://github.com/go-gitea/gitea/pull/27752 likely another case of a 1-line change not being backported.