Deprecation Notice

Hello - I’m fairly new to HTML/CSS/Javascript. I’m using Visual Studio Code to write and then publish my content. I’m not really sure what the deprecation notice means or what I need to do so that I can still upload my code through VSC. I’d love any help or being pointed to helpful resources for understanding this change. Thanks in advance!

Could you quote the deprecation notice, so we know what it’s about? From the context I guess the password deprecation for Git and API access?

@mdiddie you could take a look at this post and links to see it is similar, guessing you are talking about password depracation notices also and to switch to personal access tokens or SSH key for authentication

1 Like

Hi! So I received an email and it contained this link:

I’m pretty overwhelmed by the information provided - I had a friend help me connect my Visual Studio Code account to my Github account. I’m not a programmer by any means! I guess I’m just trying to figure out what this means in regards to how I upload my content through VSC? Do I need to change something?

Okay, so you are suggesting I should switch to a ‘personal access token.’ I have no idea what that is but I’ll look it up - if you have a good resources for learning more about what these tokens are and how to use them I’d be really appreciative! Thankyou!

So, does this seem right? First, I need to make a PAT:

And then I need to apply it to my VSC:

GitHub - Visual Studio Marketplace.

1 Like

Basically you just need to use the PAT, as @byrneh’s pointed out. This means to create a PAT (you already found the documentation on that) and use that instead of your password when VSC connects to Github. Maybe someone who’s familiar with VSC can describe how to do that?

1 Like

Create the Personal Access Token by going to Profile Icon on GitHub page > Settings > Developer settings > Personal access tokens and name it “Home PC VS Code” (or whatever you want). Leave that page open.

Go to VS Code and click the user profile symbol in the bottom left (above the settings gear icon).

Select the “GitHub” option, enter your username/email as normal, and copy-and-paste the Personal Access Token you created in the password field.

After making sure it signed in successfully, close the tab you left open with the Personal Access Token (you won’t be able to see it again).

Hope that helped :slight_smile:


I am not an active VSC, but checked the latest versions of Visual Studio Code 1.8.0 (January 26, 2021) and Git version installed.

I did a simple clone of a private repository and it successfully worked with the option to [Sign in with your browser]. when you click on this option it should launch an authentication flow in your default browser (you may need to manually switch if the focus does not swap automatically to the launched browser tab).
in the visual studio terminal window you will see message
info: please complete authentication in your browser…

In the launched browser tab you then simply confirm if already logged in or GitHub login as usual if not currently logged in to GitHub in your default browser.

It will create and cache a token behind the scenes for you, which seems the easiest for an inexperienced or user or someone unfamiliar or not wanting to configure and manage personal access tokens and SSH keys for Git access.

NOTE: If you want us use GitHub’s REST/GRAPHQL APIs you will have to use get used to using personal access tokens.

It means that typing your password on the terminal will not be supported.
You can either use a personal access token
or SSH keys (I prefer this)

What is preferable about the SSH keys?

@mdiddie, its a matter of personal choice in many ways. Its not uncommon for people who do not understand SSH and configuration to experience problems on setup or at some point later in time.
SSH can only be used for Git Actions, a personal access token is required for API access.

For SSH keys used by a human(user), as opposed to configured in server (machine account), you have the recommended option of adding an SSH passphrase, which adds an additional level of security should a malicious actor obtain your SSH private key.

There is a lot more that could be said, discussed and argued on the respective merits of the various authentication methods for each usage scenario. It would be large topic in itself to discuss.

The web auth flow (sign in with browser) seems the simplest for the beginner to be using.

Are you now working ok or still stuck after the posted replies above?

1 Like

I love it because I don’t have to input my password every-time i push or pull the same applies to my automated deployments on my server.

as @byrneh has mentioned you can use a SSH Key with a passphrase but I personally don’t like that.

1 Like

I haven’t done anything yet because I haven’t had time to go through the steps! But thanks for checking in. :slight_smile:

1 Like

I’ve got my PAT. How do I go about plugging it in to Eclipse. Surely I do not have to reset every password on every repository?

Thanks for this! I don’t actually see a ‘user profile’ icon in my Visual Studio Code platform above the gear icon on the bottom left. I’m still trying to look around for the ‘user profile.’ There are ‘User settings’ but I went through those and I still don’t see anything about a ‘Github’ option where I can enter a username/email. Any further help would be appreciated! I’ll keep looking.

Found this:

I tried that resource but have hit another brick wall. I made the PAT in Github but I cannot figure out how to apply it in VSC. I tried typing in “GitHub: Set Personal Access Token” in the command palette in VSC but nothing comes up and I don’t even see a user profile or anywhere I might be using a password. Maybe I don’t need to use the PAT in VSC? Also, after I created the PAT in Github I made a change to my website and pushed the request through to my Github website - it worked fine. Maybe it’s okay?

@mdiddie , VSC uses Git, so I would expect it to behave the same as Git Authentication and caching in Credential Manager. So prompting you to Signed in if not already signed in.
There is also some Visual Studio documentation

I’m actually not having any trouble uploading code to Github through VCS. I have created a PAT on my Github account and I’m trying to figure out if I need to change anything on my VCS account - because of the deprecation notice. So far, VCS doesn’t seem to be affected by the new PAT so I’m thinking maybe it’s good.

Came across this thread again; it’s been a while, but I’ll leave this here for future readers.

I just installed VS Code in a fresh Windows Sandbox instance, and the user profile icon is present above the settings icon - make sure you have the latest version, there are no potentially conflicting extensions, and the icon is not hidden (Right click on an empty spot in the sidebar and make sure all of the items are checked, especially “Accounts”).

User profile icon

However, the user profile icon did not have a GitHub option - to log in, I selected the Source Control icon in the sidebar, clicked Clone Repository, chose the “Clone from GitHub” option, clicked Allow on the dialog asking to sign in, and authorized GitHub through the browser. Then, my GitHub account appeared when clicking the user profile icon. (So, it seems like a PAT is no longer necessary.)

There is another extension called “GitHub Pull Requests and Issues” available separately in the extension store; I’m pretty sure it will just use the account details you already have if you’re signed in to GitHub.


This was it! I need to update Visual Studio Code and then the profile icon appeared and I was able to sync the settings and connect to Github with the PAT. Thank you so much!

1 Like