Why Are My Changes in a Forked Core Open edX Repo (edx-ora2) Not Reflected After Build?

I’m currently working with Open edX in a production build using Tutor(Sumac), and I need help understanding how to override core platform components.

What’s Working

I’ve successfully added custom plugins and extra packages using OPENEDX_EXTRA_PIP_REQUIREMENTS in my config.yml, like this:

OPENEDX_EXTRA_PIP_REQUIREMENTS:

git+https://github.com/my-org/my-plugin.git@my-branch

After building, my custom plugins install and work perfectly — so this part is fine.

The Problem

Now, I’m trying to override a core Open edX repo, specifically:

https://github.com/openedx/edx-ora2

Here’s what I’ve done:

  1. Forked the repo to my organization.

  2. Made custom changes on my own branch (my-branch).

  3. Added it to OPENEDX_EXTRA_PIP_REQUIREMENTS like this:

OPENEDX_EXTRA_PIP_REQUIREMENTS:
  - git+https://github.com/my-org/edx-ora2.git@my-branch

  1. Rebuilt the platform (tutor images build openedx && tutor local launch).

However, my changes are not showing up in the running Open edX instance — it still seems to be using the original edx-ora2 package.

Question

  • Is OPENEDX_EXTRA_PIP_REQUIREMENTS the correct way to override a core Open edX service/repo like edx-ora2?
  • Or is there a different approach required for replacing core packages that are part of the main build (e.g., via constraints or base images)?

Thanks in advance for any insights or pointers!

@sarina Could you please confirm who the current maintainers or main contacts for edx-ora2?

i think ORA2 is lightly maintained. You can always check the catalog-info.yaml file in any repo to see who the maintainers are. But I think this is more of a general Tutor question.