Ory has moved to a monorepo and what this means for contributors #1815
vinckr
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I wanted to share a behind-the-scenes change at Ory and explain what it means for contributors.
The short version: Ory now uses an internal monorepo. Your contribution workflow stays exactly the same. All OSS repositories remain public, active, and Apache 2.0 licensed.
The only thing you'll notice: When we merge your PR, it will show as "closed" (red) instead of "merged" (purple). This is because we use Copybara, Google's repository sync tool, to import your PR into our internal monorepo. We review and test there, then merge. The changes are automatically pushed to the OSS master branch, and GitHub closes your original PR. Your commits are merged and appear in the public history. We preserve commit authorship, so contributions still show up on your GitHub profile.
The label just looks different. Google's own OSS projects (like Go) work the same way.
We know the red "closed" status can feel weird. Please know that we genuinely appreciate every PR, and your work is very much part of Ory.
Our commercial products exist to fund and accelerate open source development. That model is not changing. More on our philosophy here: Ory's Open Source Commitment
If you have any questions or feedback please reply to this discussion or join our community chat.
Thank you for your contributions to Ory 🙌
Beta Was this translation helpful? Give feedback.
All reactions