User tests: Successful: Unsuccessful:
Automatically created pull request based on core-translation repository changes
Status | New | ⇒ | Pending |
Category | ⇒ | Installation Language & Strings Front End Templates (site) |
Labels |
Added:
Language Change
PR-5.3-dev
|
related to #45177 perhaps
@brianteeman Yes. I just see the code in that PR should work, but it hasn't been merged up into 5.3-dev yet. I will work on the upmerge.
Anyway, this PR here is ok, the possibly wrong branch update did not do any harm as both branches were in synch.
@tecpromotion I have just done an upmerge from 5.3-dev and then updated this PR. Now it shows zero changed files, that's expected as there were no new translation changes. Shall we now leave this PR open and the bot will add changes? Or shall we close it?
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-03-28 10:35:53 |
Closed_By | ⇒ | tecpromotion |
@tecpromotion Do you know why this PR shows as last commit a branch update from 5.2-dev? Merge branch 'joomla:5.2-dev' into translation5
If that commit message is auto generated by Git, then that was really a branch update from 5.2-dev, and that just worked fine because the 5.3-dev branch is up to date with 5.2-dev, but it would make trouble if that was not the case and 5.3-dev would be behind 5.2-dev regarding commits.
Is there something left to be changed in the translation update PR stuff?
Or will that be fixed when the default branch will be changed to 5.3-dev?