Jed Fox

The native link is the same as the “GitHub Apps” link at the moment. But maybe it would make sense to only modify the page if the “Developer Settings” link...

Working on this

An overview of the `spec.estree` syntax: - it’s mostly additive on top of the old syntax; the only thing that’s been removed is comment support. - Add an `@added([year], [proposal-slug])`...

Another note: it would be easy to generate versions of the `es2015`…`es2020` files that contain the entire spec as of that version instead of just the diffs by changing one...

I'm not the person who is going to be maintaining the specs for years to come, so if you have any suggestions for changes to the syntax, I would be...

Any opinions on what should be done with the versioned Markdown files? Should they contain the entire spec as of that version or should I figure out how to make...

How about a `.hotel.json` sharable file with a `cmd` string, and an array of environment variable names? This could be stored in repos and added with `hotel add .`

If you know the IP address for that server, you could set up a proxy from `sandbox` to that IP address.

I’m not actually a maintainer of this repo, so I think you’d be better off forking hotel for yourself and making the changes you need.

The correct way to set an env var is `MY_VAR=... hotel add ... -e MY_VAR`.