Using Copybara to keep a private fork in-sync?

[Philippe Noël]

Hi everyone,

Someone sent me Copybara and the project looks extremely interesting. It seems promising, but I couldn't quite tell if it was ideal for my workflow. I'm hoping to get some opinions on it.

I run this project: https://github.com/paradedb/paradedb. Most of our work is in the open source, and some is in a private fork of the repository which we call paradedb/paradedb-enterprise. It contains a few closed source features which we license.

So far, our workflow is "Every time we cut a release on the open-source repo, rebase the closed source repo and cut a release there as well". I was hoping there would be a good way to keep them in sync, or at least be able to tell commits ahead/behind similar to when you create a public fork.

A couple of points:

- We never want to sync from private repo to public repo

- We do make PRs to the private repo, so there needs to be a way to "rebase" of sort

- I'm hoping for this to be automated, so perhaps running Copybara in CI or something like that

Is this teh right use case?

[Agustin Prediger]

Hi Noël,

I've a very similar use case and was wondering the same question, did you managed to use copybara? Or did you go for other tool? I am analyzing git filter repo for example.

Regards,

Agustin

[Philippe Noël]

We didn't, we just manually sync them via git and it had worked well

Cheers,

Phil

Schedule a meeting with me

--
You received this message because you are subscribed to a topic in the Google Groups "Copybara OSS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/copybara-discuss/nE58f10DxTg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to copybara-discu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/copybara-discuss/b1f9c2fc-9f69-42d7-b1ba-8eeab6d4984dn%40googlegroups.com.