PR-6.2-dev Pending

User tests: Successful: Unsuccessful:

avatar laoneo
laoneo
7 Jun 2026
  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

Fixes code style issues during the Github workflow. Only issue is that no new workflow is started and the test results do not appear here. this comes from a security issue where github doesn't trigger new workflows when the bot changes something in the code base (according to Claude).

Additionally it updates all images to PHP 8.5.

Remark

In Joomla 7.0 we have to remove the phpcs dependency and code style xml file.

Testing Instructions

Check if my extra code style error is fixed in this pr and a new commit is done by the bot.

Actual result BEFORE applying this Pull Request

No code style fix and a failed workflow.

Expected result AFTER applying this Pull Request

Fix is commited to the pr and the other checks are running through.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

0564f8a 7 Jun 2026 avatar laoneo all
avatar laoneo laoneo - open - 7 Jun 2026
avatar laoneo laoneo - change - 7 Jun 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 7 Jun 2026
Category Repository
avatar richard67
richard67 - comment - 8 Jun 2026

There is another PR for the same purpose for the 5.4-dev branch: #46874

avatar laoneo laoneo - change - 9 Jun 2026
Labels Added: PR-6.2-dev
avatar laoneo
laoneo - comment - 9 Jun 2026

I saw that and was a bit hesitant to add an action for this which I never used before.

avatar Hackwar
Hackwar - comment - 10 Jun 2026

Does it also fix the files with the --diff argument?

avatar richard67
richard67 - comment - 10 Jun 2026

@laoneo Other question is why is this PR made for the 6.2-dev branch? Any new feature policy does not apply to our CI checks / GitHub actions, and to me it makes no sense to have it different in 5.4-dev/6.1-dev and 6.2-dev/7.0-dev.

avatar laoneo laoneo - change - 11 Jun 2026
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2026-06-11 07:52:15
Closed_By laoneo
avatar laoneo laoneo - close - 11 Jun 2026
avatar laoneo
laoneo - comment - 11 Jun 2026

Closing as we di it on 5.4 in #47936.

Add a Comment

Login with GitHub to post a comment