lisawolderiksen

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

worldofprasanna

Commands Reference

1. Start a new tmux named session tmux new -s terminal-capture
2. Split the screen using these commands,

• vertical split <C-b>"
• horizontal split <C-b>%

3. To navigate between the panes,

• To goto Left pane <C-b> left-key
• To goto Right pane <C-b> right-key
• To goto Top pane up-key

xpepper

My notes on the video series "London vs Chicago TDD styles" by Uncle Bob And Sandro Mancuso

The git repo of the kata is here: https://github.com/sandromancuso/cleancoders_openchat/

The "starting-point" branch is where both implementations began: https://github.com/sandromancuso/cleancoders_openchat/tree/starting-point

• The 🇬🇧 "openchat-outside-in" branch captures the tomato by tomato history of the London approach.
• The 🇺🇸 "openchat-unclebob" branch captures the tomato by tomato history of the Chicago approach.

What I like about Sandro's style 👍

joyrexus

collapsible markdown?

CLICK ME

yes, even hidden code blocks!

print("hello world!")

bittner

# Set inotify watch limit high enough for IntelliJ IDEA (PhpStorm, PyCharm, RubyMine, WebStorm).
# Create this file as /etc/sysctl.d/60-jetbrains.conf (Debian, Ubuntu), and
# run `sudo service procps start` or reboot.
# Source: https://confluence.jetbrains.com/display/IDEADEV/Inotify+Watches+Limit
# 
# More information resources:
# -$ man inotify  # manpage
# -$ man sysctl.conf  # manpage
# -$ cat /proc/sys/fs/inotify/max_user_watches  # print current value in use

PurpleBooth

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Gisleburt

#!/usr/bin/php
<?php

// Based on code by raphaelstolt and buddhamagnet https://gist.github.com/raphaelstolt/588697

class PreCommitHook {

    protected $green = "\033[0;32m";
    protected $red   = "\033[0;31m";
    protected $reset = "\033[0m";

tjamps

Basic RESTful API with Symfony 2 + FOSRestBundle (JSON format only) + FOSUserBundle + FOSOauthServerBundle

The API we are creating in this gist will follow these rules :

• The API only returns JSON responses
• All API routes require authentication
• Authentication is handled via OAuth2 with password Grant Type only (no need for Authorization pages and such).
• API versioning is managed via a subdomain (e.g. v1.api.example.com)

The API will be written in PHP with the Symfony 2 framework. The following SF2 bundles are used :

flug

function composer-update (){                                                     

  echo "-- composer update --"
  $(which hhvm) $(which composer) self-update
  $(which hhvm) $(which composer) update -vvv --profile --no-scripts &&  $(which php) $(which composer) run-script post-update-cmd
  echo "-- composer update end --"
}    

jsor

DDD, CQRS and Event Sourcing in PHP

• Broadway - Infrastructure and testing helpers for creating CQRS and event sourced applications
• EventCentric.Core - Event Sourcing and CQRS in PHP
• LiteCQRS - Small convention based CQRS library for PHP
• predaddy - Common DDD classes including an annotation driven message bus and tools for CQRS and Event Sourcing
• ProophEventSourcing - Provides basic functionality for event-sourced aggregates
• ProophEventStore - PHP 5.4+ EventStore Implementation
• ProophServiceBus - PHP Enterprise Service Bus Implementation supporting CQRS and DDD