-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename github-authentication to github #97889
Conversation
@@ -80,7 +80,7 @@ export class GitHubServer { | |||
this.updateStatusBarItem(true); | |||
|
|||
const state = uuid(); | |||
const callbackUri = await vscode.env.asExternalUri(vscode.Uri.parse(`${vscode.env.uriScheme}://vscode.github-authentication/did-authenticate`)); | |||
const callbackUri = await vscode.env.asExternalUri(vscode.Uri.parse(`${vscode.env.uriScheme}://vscode.github/did-authenticate`)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RMacfarlane Do we need to update the callback URLs also in the app registrations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's right! GitHub actually has control over this so I will reach out on getting this updated
@RMacfarlane From what I understand, there seems to be no problem renaming the extension, as far as the auth API goes since it doesn't actually know which extension calls |
Decided to take another approach: I'll create a |
Sounds good! |
This addresses the plan item:
From microsoft/vscode-pull-request-github#1788
After the rename, we can start adding features in the extension.
@RMacfarlane Need your eyes on this since renaming the extension from with an auth provider comes might have unforeseen consequences. What do you think?