Zekfad

Quick examples

• feat: new feature
• fix(scope): bug in scope
• feat!: breaking change / feat(scope)!: rework API
• chore(deps): update dependencies

Commit types

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries

mivok

#!/usr/bin/env ruby
# Sends cat pics to hipchat using either the hipchat api or kitty command
#
# Go to https://yourcompany.hipchat.com/account/api to get an API key and put
# it in '.api_token' in the same directory as this script.
#
# To send ascii cats you need the 'kitty' gem installed: gem install kitty
#
require 'hipchat'
require 'json'

fnichol

Auto-enable Local HTTP Caching in Test Kitchen

Note: total experiment and hack, looks nasty, could be awesome:

Setup

• Drop the kitchen.local.yml into $HOME/.kitchen/config.yml
• Install polipo (with Mac: brew install polipo, with Ubuntu: apt-get install polipo)
• Drop polipo-start and polipo-console somewhere useful (perhaps $HOME/bin?)

almet

Pelican 4.0 - Keep It Simple, Stupid.

I don't know if you agree with me on that, but I think that pelican does more than it should be doing currently. It was at the very beginning a simple tool, without too much corner cases, and now we have something that starts to be too big (at least to me): we cover the creation of a blog from scratch, with the quickstart thing, which generate a makefile for you, for instance, with the pelican dev-server, etc. All these things could be other projects, I think, I would go this direction if that works for you.

This way, we could keep the pelican core easy to contribute to, and we could identify who is the maintainer of which part quite easily.

Here is a proposal to make this happen:

Phase 1 - Cut some stuff out

stephenc

Puppet with Jenkins

Setup Jenkins

With Puppet:

puppet module install rtyler-jenkins

puppet apply -v -e "include jenkins"

jshell

#!/usr/bin/env python2.6
"""
A quick script to install into your `Application Support/BBEdit/Scripts` folder.
This runs PyFlakes (requires PyFlakes to be installed at `/usr/local/bin` -
try ``/usr/bin/easy_install-2.6 pyflakes==0.4.0``) and reformats the results
so that they show up in BBEdit's search results / error / warnings window. Then
the errors can be stepped through one at a time.

I've bound this to control-shift-V. You must save your Python file first before
running the check.