[Bug]: Provisioning is broken on edx-theme changes

Describe the bug that you are seeing.

This may or may not be true. I have not run into this issue myself, but I am creating a ticket based on notes from https://twou.slack.com/archives/C04A66RDPEZ/p1741695463382449.

Did anything change with Devstack and provisioning due to any changes with edx-themes? Do we need to clone this into a different directory? Why are some people running into this?

Possibilities:

• Document the issue and the manual workaround. Communicate to 2U devs.
• Fix the issue to automate the solution.

Additionally, some engineers are being added to the edx org in github without being added to the pull-all team, and thus do not have read-only access to edx-themes. I believe an SRE ticket is needed to get this access.

Did this happen on the host (your machine or the remote instance) or in the container?

TBD

Steps to reproduce.

No response

What system was this issue seen on?

TBD

No file, test, or reproducible steps are provided. Start by determining whether the failure occurs on the host or in the container and compare provisioning after edx-themes changes; confirm the required clone location and pull-all access. Done means a documented cause and workaround or an automated fix, with the needed GitHub access path clarified.