Nate Smith

love these ideas; we'll probably use yaml as we're using that now for internal extension manifests and config. a related topic is how we might expose configuration for extensions, we...

This idea is very intriguing! After discussing internally we have a few thoughts. - As useful as this could be, it's only half of the review process; to leave non-suggestion...

Marking blocked until end of august

I'm not opposed to pulling the files from `.github/ISSUE_TEMPLATE` via the content API which is something we could do for any repo (local or -R) and then mapping from yaml...

We're actively discussing improvements like this 👍 there will be limits to what we can do outside of the browser, but we do hope to add some of this functionality...

this is on our roadmap! but we hadn't opened an issue for it yet, so thank you~ we wanted to do some designs up front and see what made the...

I've renamed this as we have since added `gh pr review` (pending release) for adding a top level approve, request changes, or comment review on a given pr. However, we...

Hi! We've decided to take this on internally, so I'm going to mark this as `core`.

I tested this branch on windows and it was indistinguishable from `trunk`.

This doesn't neatly cover what `gist edit` is doing with directly opening an editor with no prompt; that's going to be a separate refactor than this effort.