ILIAS
ILIAS copied to clipboard
CI: activate captain hook and fix codestyle before commitook + Windows approved
As #4930 already adds the git hooks from captainhook this PR just removes the --dry-run
option from the captainhook.json
to automatically fix the codestyle before commiting.
As a side note:
The captainhook git hooks are executed with /usr/bin/env php
. Therefore $ which php
must point to php8.0
or php8.1
. Linting will fail under php7.4
.
Jour Fixe, 10 JAN 2022 : We highly appreciate this suggestion and accept the PR for trunk.
@lscharmer / @daniwe4 I stumbled upon an issue today (actually I thought about this some weeks ago and today I finally found time to check this): According to our documentation, a custom configuration file can be specified when installing CaptainHook
. This unversioned file in turn includes the captainhook.json
file provided by ILIAS.
If we force the installation with the specified file (like we do with this PR), the GIT hooks will be overwritten each time post-autoload-dump
is fired and the custom file is not respected anymore.
Added libs/composer/captainhook.php
to check for the captainhook.local.json.
My plan is to merge this if the trunk
is open for ILIAS 9.
@lscharmer Could you please "fix" the license header :-)?
Thx @lscharmer I'll merge this if the trunk
is open for ILIAS 9 changes.
The installation part is solved with https://github.com/ILIAS-eLearning/ILIAS/pull/4930 . This PR still provides an added value because of the changed hooks.
@lscharmer Could you please rebase this PR? Because https://github.com/ILIAS-eLearning/ILIAS/pull/4930 is now part of the trunk
, we don't need the custom scripts anymore. So the only change relevant for the trunk
integration is the change in the captainhook.json
file.
I added the JF
label to create awareness for this chang (, again).
Jour Fixe, 19 SEP 2022 : Michael wants to notify all developers about this change.
Hi @mjansenDatabay
As Technical Board, we regularly check for pull requests that have been open for a long time. Any Updates on this? Note, that you can also close this, if you are not able or if you not have the ressources to look into it in detail.
Best regards!
Hi @mjansenDatabay
As Technical Board, we regularly check for pull requests that have been open for a long time. Any Updates on this? Note, that you can also close this, if you are not able or if you not have the ressources to look into it in detail.
Best regards!
Hi @mjansenDatabay
As Technical Board, we regularly check for pull requests that have been open for a long time. This here seems to have gotten stuck on the way ;-).
Best regards! @kergomard