A Guide to StyleCI (Original)

A Guide to StyleCI (Original)

8eb6f4f9cae1b7969fc3df9d4ccd5dc4?s=128

Graham Campbell

July 25, 2017
Tweet

Transcript

  1. A Guide to

  2. The problem • Standardizing code style across your workplace or

    OSS can be hard.
  3. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI.
  4. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml.
  5. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml. • Code style can take time. ◦ No more code style reviews as part of code reviews.
  6. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml. • Code style can take time. ◦ No more code style reviews as part of code reviews. ◦ StyleCI can send fixes as PR on demand.
  7. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml. • Code style can take time. ◦ No more code style reviews as part of code reviews. ◦ StyleCI can send fixes as PR on demand. ◦ StyleCI can be configured to do this automatically!
  8. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml. • Code style can take time. ◦ No more code style reviews as part of code reviews ◦ StyleCI can send fixes as PR on demand. ◦ StyleCI can be configured to do this automatically! ◦ StyleCI can be configured to automatically merge its own PRs.
  9. The problem • Standardizing code style across your workplace or

    OSS can be hard. ◦ One-click enable from StyleCI. ◦ Configure from the browser or a .styleci.yml. • Code style can take time. ◦ No more code style reviews as part of code reviews. ◦ StyleCI can send fixes as PR on demand. ◦ StyleCI can be configured to do this automatically! ◦ StyleCI can be configured to automatically merge its own PRs. ◦ StyleCI can also be configured to directly commit the fixes!
  10. Automate code style: Don’t let code style take over your

    code reviews.
  11. History The journey of StyleCI December 2014 StyleCI created for

    my personal OSS projects. March 2015 Opened to everyone for public repos! July 2015 Launched private repo support and new website. June 2016 Added direct push support. July 2016 New PR analysis system. Q4 2014 Q1 2015 Q2 2015 Q3 2015 Q4 2015 Q1 2016 Q2 2016 Q3 2016 Q4 2016 Q1 2017 Q2 2017 Q3 2017 December 2016 Added Slack notifications.
  12. 1 Million Analyses Performed! *When I checked this morning, this

    figure stood at 993,976.
  13. Getting Started Step 1 Hit Login. Step 2 Enable Your

    Repos. Step 3 Configure and go!
  14. StyleCI is Built Using Laravel 5!

  15. Pusher StyleCI uses pusher to push changes to the web

    app. Trigger Event Bus Push
  16. What are you waiting for? Sign up today for free,

    and get unlimited public repos. Paid plans are also available for private repos. https://styleci.io/