Github repo structure advice

Question

I've been looking to setup a commit triage.

To describe with an example:

Would it be possible to make commits from the core repo trickle down to the production repo and commits to the production repo to trickle down to the Webproject repo's ? Has anyone have experience running setups like this ?

What do you mean exactly by "make commits trickle down"? Should the downstream repos have the same state as Core eventually? — Benjamin W.
– Benjamin W., Commented Nov 17, 2022 at 20:03
Yes the downstream repos should recieve the same commits as pushed to the Core repo — Kevin G
– Kevin G, Commented Nov 17, 2022 at 20:38
I meant to ask, are the downstream repos identical, or do they contain commits on top of what you have from core? — Benjamin W.
– Benjamin W., Commented Nov 17, 2022 at 21:26
You could make them forks of the core repo and then use the GitHub sync functionality? — Benjamin W.
– Benjamin W., Commented Nov 17, 2022 at 22:26

VonC · Accepted Answer · 2022-11-18 07:06:16Z

1

One possible avenue would be to use a GitHub Action on your first repository, like Git Repository Sync.

That would allow you to pushes all commits in the branch that this action is run on into any remote git repository.
Your commits would then be "propagated" to other repositories.

answered Nov 18, 2022 at 7:06

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Kevin G Over a year ago

That looks like what i was thinking of but what would be the difference between benjamin's answer of using syncing a fork ? or would this act the same as setting up an action

VonC Over a year ago

@KevinG The idea is to avoid a fork if you don't need one, to better isolate the public repo from its private upstream repository.

Collectives™ on Stack Overflow

Github repo structure advice

1 Answer 1

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Related