Jeremiah Senkpiel
Jeremiah Senkpiel
in https://github.com/nodejs/node/pull/8466 the bot somehow is adding `meta` a second time...
In order to have a bot that can automate adding/removing org users, and perhaps other things, elevated permissions from the TSC are necessary for a separate bot user to enable...
from https://github.com/williamkapke/hookbot/issues/2 we need something that uses something like https://github.com/rvagg/make-node-meeting (which relies on https://github.com/rvagg/node-meeting-agenda) to automatically make agenda issues every week, so that Rod doesn't have to lol
Getting rusoto to work with async-std streams in a context of send+sync (as imposed due to restrictions from the Tide web framework) was possible with async-compat due to the send+sync...
_I hope this is the correct issue tracker for this._ I propose we move https://github.com/Fishrock123/bob into the `nodejs` github org under a more appropriate name. "Future Streams (BOB)", maybe. This...
see https://github.com/nodejs/node/issues/906
Sometimes it will drop commits, add to many commits, not get anything at all, etc, when using `--start-ref=` and/or `--end-ref=` on io.js. For example, to get the commits in https://github.com/iojs/io.js/issues/1383#issuecomment-91247024...
I think I should make this module also contain a CLI tool installable from npm to generate from the template. Thoughts?
After further consideration, I definitely feel we should at least do `Fixes user/repo#issue`. Prevents issues from being closed with any other forks.
Been thinking about making the History --> GitHub release tool recently. However, this won't work for versions that don't have tags. Should we put commit SHAs for releases in each...