Dan Vanderkam

I like the way that [Reviewable](https://reviewable.io/) handles this:  You can drag the little arrow in the top right to adjust the width of the diff. If you click "auto",...

Here's a hack to enable the v7 pg plugin on pg v8. Use at your own peril. ```ts for (const patch of require('@google-cloud/trace-agent/build/src/plugins/plugin-pg')) { if (patch.versions === '^7.x') { patch.versions...

The workaround is fine for now, but I agree that a `parse_interval` method would be a nice enhancement to `isodate`. Handling those complexities is one of the reasons to use...

You can do this using code folding and vim. Here's a command… $ jq . foo.json | vim -c 'set syntax=json' -c 'set foldmethod=syntax' -c 'foldopen' -

Two suggestions here if you're using webpack: - If you set `devtool: 'eval-source-map'` (or anything with "eval" in it) in your `webpack.config.js`, then you'll also get coverage data for something...

Great! Let me know if there's anything I can do to help.

Nice @radekstepan, I can see burndown charts for my repo-based projects using your branch. So what you're asking from me is to add back support for repos?

In particular, would you want to switch entirely to the GraphQL API for milestones, too?

Suggestion for what the routes should be: ``` '/': 'repos', '/new/repo': 'addRepo', # preserve backwards-compatibility '/:owner/:name': 'milestones', '/:owner/:name/:milestone': 'chart', '/demo': 'demo' # match GitHub URLs '/:owner/:name/milestones': 'milestones', '/:owner/:name/milestone/:milestone': 'chart', '/:owner/:name/projects':...

Sounds good. You can fetch two types of data in a single GraphQL call, so that milestones + projects should work well. I've noticed that whenever I reload a page...