PHPackages namelesscoder/typo3-repository-gizzle - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. namelesscoder/typo3-repository-gizzle ActiveLibrary namelesscoder/typo3-repository-gizzle ===================================== GitHub Webhook Listener which releases TYPO3 extensions to TER when tags are created 1.1.4(11y ago)514[1 issues](https://github.com/NamelessCoder/typo3-repository-gizzle/issues)MITPHP Since Mar 1Pushed 11y ago1 watchersCompare [ Source](https://github.com/NamelessCoder/typo3-repository-gizzle)[ Packagist](https://packagist.org/packages/namelesscoder/typo3-repository-gizzle)[ RSS](/packages/namelesscoder-typo3-repository-gizzle/feed)WikiDiscussions master Synced 2mo ago READMEChangelogDependencies (4)Versions (8)Used By (0) [![TYPO3 GitHub Repository Releaser](https://camo.githubusercontent.com/c44802f6fffc6fc6fd2c4ac3d968f272c0569e73ca5f1e656a7380d45db65b55/68747470733a2f2f72656c656173652e6e616d656c657373636f6465722e6e65742f7479706f332d7265706f7369746f72792d67697a7a6c652d6c6f676f2e737667)](https://camo.githubusercontent.com/c44802f6fffc6fc6fd2c4ac3d968f272c0569e73ca5f1e656a7380d45db65b55/68747470733a2f2f72656c656173652e6e616d656c657373636f6465722e6e65742f7479706f332d7265706f7369746f72792d67697a7a6c652d6c6f676f2e737667) [![Build Status](https://camo.githubusercontent.com/d3ffb7f2bf2ef3eaebf13b2bd873d9ae5a0b47b45b5e73ee36f36cd2886ef49e/68747470733a2f2f696d672e736869656c64732e696f2f6a656e6b696e732f732f68747470732f6a656e6b696e732e666c7569647479706f332e6f72672f7479706f332d7265706f7369746f72792d67697a7a6c652e7376673f7374796c653d666c61742d737175617265)](https://jenkins.fluidtypo3.org/job/typo3-repository-gizzle/) [![Coverage Status](https://camo.githubusercontent.com/cd50c064a683fdd3de9f51acaf64865d2de8cd7c0e302e61f8185dfe5dcef45e/68747470733a2f2f696d672e736869656c64732e696f2f636f766572616c6c732f4e616d656c657373436f6465722f7479706f332d7265706f7369746f72792d67697a7a6c652e7376673f7374796c653d666c61742d737175617265)](https://coveralls.io/r/NamelessCoder/typo3-repository-gizzle) This project allows any GitHub-hosted repository containing a TYPO3 CMS extension to be released to the official TYPO3 Extension Repository (hereafter referred to as TER) by adding a very simple GitHub web hook. The official endpoint of this service is `https://release.namelesscoder.net`but you are welcome to install this package on your own and use that installation location as endpoint. The project uses Gizzle to listen for GitHub events and uses Gizzle TYPO3 plugins to do the actual uploading. Internally, the Gizzle TYPO3 plugins use the TYPO3 Repository Client. - - - Requirements ------------ [](#requirements) - A **public** GitHub repository containing your extension's source code. - For custom endpoints only: access to the `git` and `php` CLI commands as well as some way to serve the `web/index.php` file through HTTP/HTTPS. Installation ------------ [](#installation) 1. Edit the settings of your repository and locate "Webhooks & services". 2. Click "Add webhook" to create a new hook. 3. In "Payload URL", fill in the endpoint URL you wish to use. The default URL is `https://release.namelesscoder.net` 4. Add your unique credentials and information to the URL. There are two possible URL formats: - If your GitHub repository name is **not the same** as your TER extension key, a URL like `https://release.namelesscoder.net/my_extension/user:password`. must be used - which will release the repository as key `my_extension`. - If your GitHub repository is already named the same as your extension key you can leave out that part of the URL and use a shorter URL like `https://release.namelesscoder.net/user:password`. - Alternatively, if you feel more comfortable with it and the endpoint supports it, use `https://username:password@release.namelesscoder.net/my_extension`. This method only works if the server supports the `authnz_external_module`or corresponding external authentications - see below. 5. Enter a "Secret". We use a fixed secret for now - enter the text `typo3rocks`. 6. Leave the "Which events..." selectors as-is. We only need the `push` event. Unfortunately there is no way to isolate an event that only gets dispatched when you create new tags - which is why we have to listen to all `push`es. We simply ignore those that do not refer to a tag. Security -------- [](#security) Because your credentials are included in the URL, we are doing the following on the default endpoint and you should definitely do the same if you create one: - The URL is protected by SSL. - The full URL of requests is never logged. Please note that this credentials-in-URL approach is considered *temporary* and is only implemented because there currently are no other ways. The end goal is to use a token solution both for the "Secret" that is currently fixed, as well as for the credentials that must be passed to TER. The former will be solved by creating an official GitHub Service but the latter will depend on work that has to be done on TER or even TYPO3 SSO itself. If your web server supports it (Apache does via `authnz_external_module`) then you can register an external authenticator (change/move the path if needed): ``` DefineExternalAuth fake environment /var/www/release.namelesscoder.net/fake-auth.sh ``` ...which goes in your virtual host or root server configuration. The `fake-auth.sh`script is a dummy that allows any username and password to be authenticated - and if done this way, this project will instead read those (fake) credentials. This means you can specify the credentials to use when uploading to TER, as `https://username:password@release.namelesscoder.net/my_extension`. Usage ----- [](#usage) To create a new TER release from your GitHub repository simply create a new tag and push it. The uploader will then use the message of the commit you tag as the upload comment on TER. To create and push a new tag: ``` git tag 1.2.3 git push origin 1.2.3 ``` Which creates a new tag called `1.2.3` and pushes it to the remote called `origin`. Viewing results --------------- [](#viewing-results) The results of uploads triggered this way can be read in two different places: - The **publicly available** message that the release was created gets added as a comment to the commit that was HEAD of the repository when tagging. - The **privately available** debugging information can be viewed by locating the "Webhooks & services" panel as described in the installation section, and clicking the URL that was added. A short list of most recent transactions is displayed and clicking each one will allow you to read any technical errors. Behavior -------- [](#behavior) The behavior of this plugin is very easily described: 1. Whenever you push to GitHub, we receive an event. 2. We analyse the Payload HEAD: - If it is not a new tag we exit. - If it is a new tag we upload a new release. 3. We set a "success" status flag on the commit you tagged. 4. We add a comment to the commit you tagged, saying it was released to TER. 5. We assign a bit of debugging information and send our response to GitHub. The whole process should only take a couple of seconds, depending on how large your extension is. If at any point during the process an error occurs, it is caught and can be inspected in the web hook response as described above. ### Health Score 28 — LowBetter than 54% of packages Maintenance16 Infrequent updates — may be unmaintained Popularity10 Limited adoption so far Community7 Small or concentrated contributor base Maturity68 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~1 days Total 7 Last Release 4083d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/f5c01fb202269a6d9ba372c482874512d0246da99934592cdba1869a1776c4c1?d=identicon)[NamelessCoder](/maintainers/NamelessCoder) --- Top Contributors [![NamelessCoder](https://avatars.githubusercontent.com/u/2228052?v=4)](https://github.com/NamelessCoder "NamelessCoder (27 commits)") --- Tags phppluginreleasegithubgitwebhookHOOKtypo3 ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/namelesscoder-typo3-repository-gizzle/health.svg) ``` [![Health](https://phpackages.com/badges/namelesscoder-typo3-repository-gizzle/health.svg)](https://phpackages.com/packages/namelesscoder-typo3-repository-gizzle) ``` ### Alternatives [ramsey/conventional-commits A PHP library for creating and validating commit messages according to the Conventional Commits specification. Includes a CaptainHook action! 1931.2M122](/packages/ramsey-conventional-commits)[nilportugues/php_backslasher Adds all PHP internal functions to its namespace by adding backslash to them. Improves the application's performance when OPCache is on. 889.3k18](/packages/nilportugues-php-backslasher)[pestphp/pest-plugin-stressless Stressless plugin for Pest 67792.6k16](/packages/pestphp-pest-plugin-stressless)[nilportugues/php_todo Looks into the code using a user-defined list of to-do phrases and stops commit if the total amount increased or is above a threshold. 1210.0k](/packages/nilportugues-php-todo) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)