title: How to correctly use GitHub's authentication token?
body: <p>When I pushed to my repository using the bash terminal, GitHub sent me an email:</p>
  <blockquote>
  <p>[GitHub] Deprecation Notice<br />
  Hi,</p>
  <p>You recently used a password to access the repository at 
  with git using git/.</p>
  <p>Basic authentication using a password to Git is deprecated and will
  soon no longer work. Visit
  <a href="https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/" rel="noreferrer">https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/</a>
  for more information around suggested workarounds and removal dates.</p>
  <p>Thanks, The GitHub Team</p>
  </blockquote>
  <p>So I tried figuring out how to use the auth token, but <a href="https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token" rel="noreferrer">this</a>, <a href="https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow" rel="noreferrer">this</a> and <a href="https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets" rel="noreferrer">this</a> page didn't really help.</p>
  <p>Once I generate a token that looks like this, <code>ff35995a9624470a855520c573972d2f1812843</code>, I understand that I'm supposed to be able to do a <code>git push --all</code>, then type my username and enter the token to be able to authenticate.<br />
  But this would mean that I need to store this token in plain text or in some password manager. That just seems wrong. Or is my understanding of this whole process flawed?</p>
  <p>How do I securely use this token instead of a password? I remember <a href="https://www.sourcetreeapp.com/" rel="noreferrer">SourceTree</a> had something that I think was a provision for storing such a token, but how would one do it via the Linux terminal securely?</p>