JakeGinnivan

• 12pm - The Kernel (~1hour) (2pm close)
• 1pm - Fourpure (~45mins)
• 1:30pm - Partizan (~45hour)
• 2:30pm - Brew By Numbers (~1hour)
• 3:30pm - Southwark Brewing Co (~30mins) (5pm close)
• 4:15pm - Anspach & Hobday/Bullfinch Brewery (~1hour) (6pm close)
• 6pm - Bottleshop

Map of where they all are

aaronpowell

$(document).on('click', '#showInvestigated', function () {
    window.location = '@Html.Raw(Url.Action("StoreErrors"))';
});

gist:5402269

    public class VolatileJournal : IJournal
    {
        private readonly StringBuilder log;

        public VolatileJournal()
        {
            log = new StringBuilder();
        }

        public string[] GetExecutedScripts()

andreasohlund

ReleaseNotesCompiler

In order to improve the quality for our release notes we'll generate them based on the relevant github issues.

* This is a separate tool from GFV
* The build server will compile the release notes either for each commit or daily
* Build will fail if release notes can't be generated
* All closed issues for a milestone will be included
* All issues must have one of the following tags Bug|Feature|Internal refactoring
* For now the text is taken from the name of the issue

khellang

# Utilities
cinst 7zip
cinst ConEmu

# Fonts
cinst SourceCodePro

# Coding
cinst git
cinst P4Merge

JakeGinnivan

I have been doing a heap of reading about semver and how you can include build meta-data and other things, but I am really struggling to find a way to fit SemVer and Continous Delivery together.

Currently I am the primary maintainer or a main contributor for for:
https://github.com/TestStack/White
https://github.com/JakeGinnivan/VSTOContrib
https://github.com/DbUp/DbUp
https://github.com/Code52/DownmarkerWPF
https://github.com/TestStack/ConventionTests

And quite a few other smaller projects (https://github.com/JakeGinnivan?tab=repositories)

ryanseddon

mocha --compilers js:babel/register,js:./test/css-modules-compiler.js --recursive -w

iammerrick

import React from 'react';

const toPromise = (load) => (new Promise((resolve) => (
  load(resolve)
)));

class LazilyLoad extends React.Component {

  constructor() {
    super(...arguments);

mat-mcloughlin

[AttributeUsage(System.AttributeTargets.All, AllowMultiple = true, Inherited = true)]
public class ಠ_ಠAttribute : Attribute
{
  public ILog Log { get; set; }
 
  public ಠ_ಠAttribute()
  {
    Log.Info("This code is bad and you should feel bad");
  }
}

samwize

// # Mocha Guide to Testing
// Objective is to explain describe(), it(), and before()/etc hooks

// 1. `describe()` is merely for grouping, which you can nest as deep
// 2. `it()` is a test case
// 3. `before()`, `beforeEach()`, `after()`, `afterEach()` are hooks to run
// before/after first/each it() or describe().
//
// Which means, `before()` is run before first it()/describe()