Automate keeping this fork up to date #36

Open
opened 2023-03-29 16:28:36 +00:00 by delvh · 2 comments
Owner

Act version

Irrelevant

Feature description

I think maintaining this fork would be a lot easier if changes upstream were automatically added here as well.

So far, I've found two existing bots for that (

) that are both written for GitHub.com exclusively and in JS.
It might make sense to write a Bot based on that (in whatever language, i.e. Go), and offer it as one of Giteas official repos as well as this repo is not the only one that would benefit from having that sort of automation.

### Act version Irrelevant ### Feature description I think maintaining this fork would be a lot easier if changes upstream were automatically added here as well. So far, I've found two existing bots for that ( - https://github.com/wei/pull - https://github.com/backstrokeapp/server ) that are both written for GitHub.com exclusively and in JS. It might make sense to write a Bot based on that (in whatever language, i.e. Go), and offer it as one of Giteas official repos as well as this repo is not the only one that would benefit from having that sort of automation.
Owner

TBH, based on past experience with resolving conflicts when merging upstream updates, I don't think it can be that simple. The upstream is not designed as a library, so many disruptive updates can occur.

To be clear, I have no objections to your idea, I just think we may need a better time to do this.

TBH, based on past experience with resolving conflicts when merging upstream updates, I don't think it can be that simple. The upstream is not designed as a library, so many disruptive updates can occur. To be clear, I have no objections to your idea, I just think we may need a better time to do this.
Member

I think the idea of a "mirror plus some commits on top" is a idea worth exploring on its own for gitea itself. I would certainly have a few uses for such a mechanism myself.

I think the idea of a "mirror plus some commits on top" is a idea worth exploring on its own for gitea itself. I would certainly have a few uses for such a mechanism myself.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act#36
No description provided.