Latest blog entries
The Art of Writing a Blogpost
Mar 09 2017 : Matias Vera
Feb 14 2017 : Felipe Ripoll
Do you need a blazing fast reverse geocoder? Enter offline-geocoder!
Jan 18 2017 : Roberto Romero
MongooseIM has RESTful services!! Here I show how you can use them in an iOS application.
Dec 13 2016 : Sergio Abraham
20 Questions, or Maybe a Few More
Nov 16 2016 : Stephanie Goldner
Because conferences and meetups are not just about the technical stuff.
Nov 01 2016 : Pablo Villar
Sharing some light on how it is to partner with us.
Oct 27 2016 : Inaka
How to easily play a sound in Android
Oct 25 2016 : Giaquinta Emiliano
We're publishing our work guidelines for the world to see.
Oct 13 2016 : Brujo Benavides
Using niffy to simplify working with NIFs on Erlang
Oct 05 2016 : Hernan Rivas Acosta
How to write clear function signatures, yet expressive, while following Swift 3 API design guidelines.
Sep 16 2016 : Pablo Villar
How to automatically trigger rails tests with a Jenkins job
Sep 14 2016 : Demian Sciessere
A description of our usual stack for building REST servers in Erlang
Sep 06 2016 : Brujo Benavides
Using Erlang's External Term Format
Aug 17 2016 : Hernan Rivas Acosta
Integrating our Android linter with Github's pull requests
Aug 04 2016 : Fernando Ramirez and Euen Lopez
Introducing how to implement passwordless login with phoenix framework
Jul 27 2016 : Thiago Borges
Our newest game to test your Beam Skills
Jul 14 2016 : Brujo Benavides
Three Open Source Projects, one App
Jun 28 2016 : Andrés Gerace
Running credo checks for elixir code on your github pull requests
Jun 16 2016 : Alejandro Mataloni
Thoughts on rebar3
Jun 08 2016 : Hernán Rivas Acosta
Some time ago we started developing using Elixir language and we loved it! As usual, we wanted to focus on code logic rather than on code style, so we also started using Credo a great tool to examine elixir code developed by René Föhring (@rrrene)
So far so good, but we all make mistakes, and sometimes developers send a pull request without fixing all credo warnings/errors. A few times of this happening was enough proof to consider that we needed a tool to automatically check the code whenever a pull request was created.
So that's how CredoCI was born.
CredoCI is basically a service that integrates with your public repositories, so that each time there is a new pull request, it runs credo service against the PR's code reporting errors/warnings as github comments.
After you sign up with your Github account, a list of your public repositories will be displayed, allowing you to [de]activate
CredoCI service for it.
CredoCI would use the
.credo.exs file present in the PR's branch, if any. Otherwise, it will use the default credo configuration.
And...that's all! Simple, but very useful, right?
We are already using it to check our public repos like Dayron(which I really recommend to take a look at)
CredoCI is still in version 0.9.0, so if you have any questions, suggestions or issues to report, use github issues or talk directly with us in our public hipchat room. We're waiting for your feedback.