Add a backport bot #9340

Closed
opened 2025-11-02 08:35:56 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @silverwind on GitHub (Aug 3, 2022).

Manual backporting is cumbersome when commits are cherry-pickable. I think we could use trop or similar to automatically create backports based on labels. See for example this PR.

Not entirely sure if trop is suitable, but there are other bots/actions as well for cherry-picking, like https://github.com/marketplace/actions/xealth-cherry-picker which creates PRs or https://github.com/marketplace/actions/cherry-pick-squashed-prs which directly pushes to branch.

Originally created by @silverwind on GitHub (Aug 3, 2022). Manual backporting is cumbersome when commits are cherry-pickable. I think we could use [trop](https://github.com/electron/trop) or similar to automatically create backports based on labels. See for example [this PR](https://github.com/electron/electron/pull/35194#issuecomment-1203670589). Not entirely sure if trop is suitable, but there are other bots/actions as well for cherry-picking, like https://github.com/marketplace/actions/xealth-cherry-picker which creates PRs or https://github.com/marketplace/actions/cherry-pick-squashed-prs which directly pushes to branch.
GiteaMirror added the type/miscellaneoustype/proposal labels 2025-11-02 08:35:56 -06:00
Author
Owner

@mscherer commented on GitHub (Aug 4, 2022):

Since there is a plan to move to self-hosting gitea (as far as I know), I think the bot should be compatible with gitea

@mscherer commented on GitHub (Aug 4, 2022): Since there is a plan to move to self-hosting gitea (as far as I know), I think the bot should be compatible with gitea
Author
Owner

@silverwind commented on GitHub (Aug 4, 2022):

Since there is a plan to move to self-hosting gitea (as far as I know), I think the bot should be compatible with gitea

If there's nothing suitable, I wouldn't oppose to just use these GitHub actions for now. Developing bots takes much time etc :)

@silverwind commented on GitHub (Aug 4, 2022): > Since there is a plan to move to self-hosting gitea (as far as I know), I think the bot should be compatible with gitea If there's nothing suitable, I wouldn't oppose to just use these GitHub actions for now. Developing bots takes much time etc :)
Author
Owner

@silverwind commented on GitHub (Mar 4, 2023):

Looks this is now implemented with recent changes to Gitea bot.

@silverwind commented on GitHub (Mar 4, 2023): Looks this is now implemented with recent changes to Gitea bot.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9340