Here are suggested hooks for integration manager repository, in a composer based PHP project.
The IM has all the developer hooks, more the prepare-commit-msg to intercept unwanted merges.
Here are suggested hooks for integration manager repository, in a composer based PHP project.
The IM has all the developer hooks, more the prepare-commit-msg to intercept unwanted merges.
| # /path/to/repos/apache.conf | |
| ## Git HTTP(s) backend (aka Git Smart HTTP) and Gitweb | |
| ## =================================================== | |
| ## See https://git-scm.com/docs/git-http-backend | |
| ## See https://git-scm.com/book/be/v2/Git-on-the-Server-Smart-HTTP | |
| ## See https://git-scm.com/docs/gitweb | |
| # Git over https |
| # /path/to/docs/apache.conf | |
| Alias /docs /path/to/docs | |
| <Directory /path/to/docs> | |
| Options -Indexes +FollowSymLinks | |
| DirectoryIndex guide-README.html | |
| AllowOverride None | |
| Require all granted | |
| </Directory> |
| # /path/to/application/apache.conf | |
| # UTF-8 forever! | |
| # ============================== | |
| AddDefaultCharset utf-8 | |
| # Main URL rewriting rules | |
| # ============================== | |
| RewriteEngine On | |
| # If $showScriptName is false in UrlManager, do not allow accessing URLs with script name |
Here are hooks for an integration bare repository.
The repository is intended to be reached via HTTP(s) only and the access is filtered by the REMOTE_USER env var.
As post-receive notification system, the script suggested at http://www.fclose.com/1473/setting-up-git-commit-email-notification/ has been chosen.
Here are the hooks for a blessed repository.
The post-merge hook generate the docs using yiisoft/yii2-apidoc
and measure the LOCs with
sebastianbergmann/phploc.
As post-receive notification system, the script suggested at http://www.fclose.com/1473/setting-up-git-commit-email-notification/ has been chosen.
Here are suggested hooks for a developer repository, in a composer based PHP project.
The pre-commit avoids direct commits in masterbranch and performs quality checks (qa script) on changed files,
blocking the poor quality code.
The post-merge install new versions of packages on composer.lock changes and perform a new QA check on incoming code.
The quality checks are based on PHP Mess Detector and PHP CodeSniffer