How many times did you receive an issue about a bug already fixed in a new release?
How many times your customers fix a bug on their side when they could enjoy the latest version with official bug fixes and new features?
Discussing with some Akeneo developers, they asked me: “How can we know when a new release of <amazing-Akeneo-package> is published?”.
It’s pretty simple, as GitHub dispatch events for every action done into a repository or an organization.. so I’ve built a minimalist bot in 2 hours that provide the feature for free, because I love open source you know :)
Tell me more!
Then install dependencies using Composer:
composer install, this will create a
vendor folder and configure the class autoloader.
Then copy/paste the distributed
.env.dist file and fill it with Twitter credentials (to get credentials, you have to register a new application on Twitter).
What’s the f*ck is this @ expression in your Twitter message?
MicroEngine class I’ve created allows the access to every data contained by the Release object from GitHub API (you only need to use Camel case instead of Snake case). You can find the list of available properties in the PHP project I use to map GitHub Json responses to a developer-readable Release object.
In my case,
@htmlUrl retrieves the
html_url property from GitHub release, i.e the release HTML page url!
I want to contribute!
Please don’t. For real I don’t have too much time to spend on this kind of baby project, I encourage you to fork it and have fun with it like I had :)
Happy coding everyone!
PS: If you have something to share, feel free to do it here, on GitHub or Twitter ;)