[ ] I have linked the issue that this PR fixes in the "Development" section of the sidebar.
[ ] I have checked the "Files Changed" tab and confirmed that the changes are what I want to make.
[ ] I have written tests for my code.
[ ] The PR title starts with "Fix #bugnum: " or "Fix part of #bugnum: ...", followed by a short, clear summary of the changes.
[ ] I have assigned the correct reviewers to this PR (or will leave a comment with the phrase "@{{reviewer_username}} PTAL" if I can't assign them directly).
Testing doc (for PRs with Beam jobs that modify production server data)
[ ] A testing doc has been written: ... (ADD LINK) ...
[ ] (To be confirmed by the server admin) All jobs in this PR have been verified on a live server, and the PR is safe to merge.
Proof that changes are correct
Proof of changes on desktop with slow/throttled network
Proof of changes on mobile phone
Proof of changes in Arabic language
PR Pointers
Never force push! If you do, your PR will be closed.
Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
Overview
Essential Checklist
Please follow the instructions for making a code change.
Testing doc (for PRs with Beam jobs that modify production server data)
Proof that changes are correct
Proof of changes on desktop with slow/throttled network
Proof of changes on mobile phone
Proof of changes in Arabic language
PR Pointers