User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Status | New | ⇒ | Pending |
Category | ⇒ | Unit Tests Repository Administration com_associations com_banners com_cache com_categories com_checkin com_config com_contact com_content com_contenthistory com_fields |
Title |
|
OK, my next steps would be close this PR and undo my last upmerge commit.
OK, my next steps would be close this PR and undo my last upmerge commit.
Better close this PR, delete your branch "upmerges/2024-10-09" locally, and if in your repo on GitHub also there, then create the branch again based on the current 6.0-dev branch and start with that.
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-10-09 07:35:47 |
Closed_By | ⇒ | Bodge-IT | |
Labels |
Added:
Unit/System Tests
PR-6.0-dev
|
Closing as suggested
This PR is wrong. The 5.2-dev branch was merged into the branch of this PR with a squash commit, so this PR shows only one commit for the merge. It should have been done with amerge commit so this PR would show all commits in the 5.2-dev branch since the last upmerge plus the commit of the merge.