3 ms·
Totally get it. I’ve passed feedback on to the team so (hopefully) the CLI app will be be clearly from GitHub soon (we need to transfer it to the regular GitHu
by filmgirlcw 4y ago
Totally get it.
I’ve passed feedback on to the team so (hopefully) the CLI app will be be clearly from GitHub soon (we need to transfer it to the regular GitHub org and then there hopefully won’t be any confusion). GitHub Next exists in a different org from GitHub proper for lots of reasons, but we should definitely make it more clear that those experiments are still from GitHub.
- vlovich123 4y agoDoing it under a liberated domain under GitHub.com sounds like it would work (still a separate org but it’s a signal that this is from main GitHub)
- RulerOf 4y agoFYI, after digging down a few links from there and winding up at the GitHub Next org page[1], seeing the verified email next@github.com and the official site link to https://githubnext.com https://githubnext.com was enough validation for me. Can't wait for Voice Copilot :) 1: https://github.com/githubnext https://github.com/githubnext
- rjzzleep 4y agoTo me the auth flow looks wrong. The CLI oauth would get act on your behalf, but the website to apply for access should not under any circumstance do that. Maybe it's just copy and pasted from somewhere, but it looks wrong to me regardless.
- Kye 4y agoIt seems like one organization being able to specify a relationship with another, possibly with the ability to set a list of approved permissions, would solve this.