Testing to see what happens when I change a source string#31276
Testing to see what happens when I change a source string#31276pomegranited wants to merge 1 commit intoopenedx:masterfrom
Conversation
without re-extracting the source messages.
|
Thanks for the pull request, @pomegranited! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate. |
|
@pomegranited Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future. |
|
What were you expecting to see in this PR? Did it happen or not? |
|
Hi @jansenk -- I was hoping the CI build would fail, because I'd changed a source string without also submitting an update to the compiled strings. But it didn't fail, all checks were green. So that means we don't have any CI checks for this, and so keeping source strings extracted, compiled, and synced to Transifex must be handled by the transifex bot? |
without re-extracting the source messages.
Description
Draft OSPR to test whether/how our CI quality checks detect an altered source string that hasn't been pulled into the compiled messages.
Supporting information
cf openedx/openedx-proposals#367 (comment)
Testing instructions
CI should be enough
Deadline
None -- do not merge :)