gitea-backporter icon indicating copy to clipboard operation
gitea-backporter copied to clipboard

:tea: A script that looks for PRs in Gitea that need to be backported and creates the backport PR for them

Results 9 gitea-backporter issues
Sort by recently updated
recently updated
newest added

The bot does a lot more than just backporting, so I'd say a rename to a more fitting name is in order. Maybe also lowercase the org name to match,...

I'm often not sure whether a PR is cherry-pickable without conflict or not. It would be useful to have two new labels to indicate the cherry-pick-ability: - `automated-backport-possible` - `automated-backport-impossible`...

https://github.com/go-gitea/gitea/pull/25721#issuecomment-1624581483

See https://github.com/go-gitea/gitea/pull/29191. The bot did not remove the label after re-request which lifted the block. Maybe GitHub has changed something about this API because I recall this did work before....

https://github.com/go-gitea/gitea/pull/27503 is a clean cherry-pick against both 1.21 and 1.20, but the bot failed for unknown reasons. Here's how I do it, maybe the bot tries it differently? ```sh git...

![image](https://github.com/GiteaBot/gitea-backporter/assets/18380374/b23f3ce0-0b2d-4ddd-87c6-b75b8b37d051) I think this is caused by that v1.19 does not support any more, so bot can not find the correct milestone. Maybe we can add a check of this...

The bot could accept a mention with a command like ``` @GiteaBot run `make fmt` ``` If this exact syntax is matched, check out the branch, run the command, and...

![image](https://user-images.githubusercontent.com/20454870/224379130-368bdfda-493b-4111-bb26-d27f436474af.png)