PHPackages                             pensiero/github-tools - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. pensiero/github-tools

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

pensiero/github-tools
=====================

Helpful GitHub tools packed in a ZF2 module

v1.0.3(9y ago)044[1 issues](https://github.com/pensiero/github-tools/issues)BSD-3-ClausePHPPHP &gt;=5.6

Since Feb 27Pushed 9y ago1 watchersCompare

[ Source](https://github.com/pensiero/github-tools)[ Packagist](https://packagist.org/packages/pensiero/github-tools)[ Docs](https://github.com/pensiero/github-tools)[ RSS](/packages/pensiero-github-tools/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (6)DependenciesVersions (4)Used By (0)

GitHub Tools module for ZF2
===========================

[](#github-tools-module-for-zf2)

Created by Oscar Fanelli

Introduction
------------

[](#introduction)

ZF2 module that provides tools to connect your application with your GitHub repository via ZF2 console. What you can do?

- Automatically create a new PR (from `develop` to `master`) and a new draft release (its notes will contains the diff commits between `develop` and `master`)
- Mark a repository as deployed

Installation
------------

[](#installation)

GitHub Tools work with composer. Make sure you have the composer.phar downloaded and you have a composer.json file at the root of your project. To install it, add the following line into your composer.json file:

```
"require": {
    "pensiero/github-tools": "~1.0"
}

```

Requirements
------------

[](#requirements)

- PHP5.6+
- [zend-mvc 2.7](https://github.com/zendframework/zend-mvc)
- [zend-console 2.6](https://github.com/zendframework/zend-console)

Configuration
-------------

[](#configuration)

Use the [config/github-tools.local.php.dist](config/github-tools.local.php.dist) as blueprint configuration file: copy it to the `config/autoload` directory of your ZF2 application and remove the `.dist` extension from its name.

If you are using environment variables to store sensible informations of your projects (like auth keys) you can use the following ones:

- `GITHUB_ACCESS_TOKEN` will override the `github_access_token` config
- `ENV` will override the `environment` config
- `PROTOCOL` and `HOST` will be combined in order to override the `target_url` config

> NOTE: if `github_from_branch` === `github_to_branch`, PR creation will be skipped and the release will be created with the diff commits against the latest release

Available commands
------------------

[](#available-commands)

### Mark a repository as deployed

[](#mark-a-repository-as-deployed)

Will be marked the configurated GitHub repository as deployed

```
php public/index.php github mark-repo-deployed

```

### Create a new release

[](#create-a-new-release)

Will be created a new PR from `github_from_branch` to `github_to_branch` named with the new version name. Will be created a new draft release for `github_to_branch` named with the new version name.

**Major**

New version name: get the latest release name and increment the *major* part of 1, according to [semver](http://semver.org/).

Example:

- Latest release: `v2.0.3`
- New release: `v3.0.0`

```
php public/index.php github create-major-release

```

**Minor**

New version name: get the latest release name and increment the *minor* part of 1, according to [semver](http://semver.org/).

Example:

- Latest release: `v2.0.3`
- New release: `v2.1.0`

```
php public/index.php github create-minor-release

```

**Patch**

New version name: get the latest release name and increment the *patch* part of 1, according to [semver](http://semver.org/).

Example:

- Latest release: `v2.0.3`
- New release: `v2.0.4`

```
php public/index.php github create-patch-release

```

###  Health Score

26

—

LowBetter than 43% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community5

Small or concentrated contributor base

Maturity60

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 ~12 days

Total

3

Last Release

3339d ago

### Community

---

Top Contributors

[![pensiero](https://avatars.githubusercontent.com/u/2010696?v=4)](https://github.com/pensiero "pensiero (17 commits)")

---

Tags

githubgithub-apigithub-pageszend-frameworkzend-framework2zendframework-consolezf2zf2-module

### Embed Badge

![Health badge](/badges/pensiero-github-tools/health.svg)

```
[![Health](https://phpackages.com/badges/pensiero-github-tools/health.svg)](https://phpackages.com/packages/pensiero-github-tools)
```

###  Alternatives

[voku/php-hooks

A fork of the WordPress filters hook system rolled in to a class to be ported into any PHP-based system

7637.3k3](/packages/voku-php-hooks)[fabiopaiva/zf2-doctrine-autocomplete

Provides a autocomplete form for ZF2 and Doctrine2.

104.9k](/packages/fabiopaiva-zf2-doctrine-autocomplete)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
