commit | b32116de3031b064d588376fd7099c82865544c3 | [log] [tgz] |
---|---|---|
author | Michael Große <[email protected]> | Fri Jun 14 12:59:01 2024 +0200 |
committer | Michael Große <[email protected]> | Fri Jun 14 13:01:43 2024 +0200 |
tree | df3d29a82a3041de66b334ac67640a59087737fb | |
parent | ed47ecfc46779fa501b6ed1520d4393003d14ce6 [diff] |
Add styles performance budget for GrowthExperiments extension We have CI failing on this test for GrowthExperiments with the styles budget being exceeded. On changes that do not touch production code at all. I do not know how this can happen in the first place, or whether fixing it this way is sensible, but we need to unblock our CI. Change-Id: I178cb7ff6f111a11e9b6060960548e65d1c7d3c0
See https://www.mediawiki.org/wiki/Skin:Vector.
See skin.json.
Also see configuration.md
It is recommended to use nvm to use the version of node defined in .nvmrc
during local development. This ensures consistency amongst development environments.
We strive for compliance with MediaWiki conventions:
https://www.mediawiki.org/wiki/Manual:Coding_conventions
Additions and deviations from those conventions that are more tailored to this project are noted at:
https://www.mediawiki.org/wiki/Reading/Web/Coding_conventions
A pre-commit hook is installed when executing npm install
. By default, it runs npm test
which is useful for automatically validating everything that can be in a reasonable amount of time. If you wish to defer these tests to be executed by continuous integration only, set the PRE_COMMIT
environment variable to 0
:
$ export PRE_COMMIT=0 $ git commit
Or more succinctly:
$ PRE_COMMIT=0 git commit
Skipping the pre-commit tests has no impact on Gerrit change identifier hooks.
See hooks.txt.