Hello everyone!
We have a new process for handling code drift on the edx-platform repo. It’s split into 2 parts:
- Github Project board that we need to keep up-to-date in order to give us a holistic view of the state of the code drift.
-
Github Action automation that creates sync PRs for any changes that happen upstream that we need to pull in to our forks. It is currently configured for our
opencraft-release/palm.1
branch.
Please check out the new How to handle Code Drift section in the handbook for all the details on how to keep the board up-to-date for the internal PRs you create, to upstream as much of the work as possible and help us stay on top of any Code Drift that we introduce.