Benjamin E. Coe

Results 67 issues of Benjamin E. Coe

## Background I've been developing automated release tooling that allows for releases from multiple branches. The goal being that you could support the main release line, along with back-porting security...

@sindresorhus, @satazor in newish versions of Node.js, what issues continue to exist in `spawn` that would motivate the use of `execa` or `cross-spawn`. I wonder if: 1. some of the...

we're using highlights for the syntax highlighting of npm READMEs now, and have extended it so that grammars can be installed from npm modules: https://github.com/atom/highlights/pull/14 Would you mind publishing `atom-language-erlang`...

Currently if one were to set a "content-type" header and a "Content-Type" header, the two are not equivalent. I've seen libraries like `express` approach this differently, such that `headers` are...

type: feature request

the BREAKING CHANGE is greedy, in that it consumes text until the end of the commit message after the `:`; this perhaps makes sense for the body? but for the...

design

If you run stats.js without specifying a configuration file, configuration will be loaded from environment variables name-spaced with STATSD_: ``` bash STATSD_graphitePort=2003 STATSD_graphiteHost=carbon.hostedgraphite.com STATSD_port=8125 STATSD_graphite_legacyNamespace=false STATSD_graphite_globalPrefix=bananas STATSD_flushInterval=5000 ``` Creates ```...

I notice in the [git documentation](https://git-scm.com/docs/git-commit#_discussion) that they refer to the first line of the commit message as a `` and the longer body of the commit message as a...

meeting-agenda

A few folks have pointed out that "feat" can be confusing, is adding ambiguity worth saving three characters? CC: @jskeet, and @bshaffer, who brought this up.

meeting-agenda

## Proposal I would like to suggest that we have our first monthly meeting in October, where: 1. start to figure out some governance for this project. 2. divide up...

process

Prior to the updates in https://github.com/googleapis/nodejs-vision/pull/1016, only the `product sets` suite of tests was running in integration. When all tests were enabled, many flaky/failing tests have been surfaced. --- _Note:...

type: bug
api: vision
priority: p3