临时设备上能否通过用户名/密码向GitHub推送代码？技术方案咨询

Hey there! I totally get your situation—you’re on a temporary laptop and don’t want to leave any personal traces behind, but GitHub’s old username/password auth isn’t working anymore. Let’s break this down clearly:

First, that error message you’re seeing is definitive:

remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.

Unfortunately, you can’t use your regular GitHub username and password to push code anymore—GitHub permanently retired password-based authentication for Git operations back in 2021. But don’t stress, there’s a secure, temporary-friendly workaround tailored to your needs:

• Generate a short-lived Personal Access Token (PAT)
  Hop into your GitHub account settings and create a new PAT. Only check the permissions you absolutely need (at minimum, the repo scope for private repos, or public_repo for public ones). The critical part here is setting a super short expiration time—like 30 minutes or 1 hour. This way, even if the token accidentally lingers in the terminal history, it’ll be useless right after you finish your push.

• Use the PAT directly for your push
  When Git prompts you for your username, enter your regular GitHub handle. When it asks for a password, paste your short-lived PAT instead. You don’t need to save this token to the laptop’s credential manager—just use it once for your push, and it’ll expire automatically.

If you’re extra cautious about terminal history, you can also use this one-time URL format to push:

git push https://<your-username>:<your-short-lived-pat>@github.com/<your-username>/<repo-name>.git

Just make sure to clear your terminal history afterward, or use a terminal that doesn’t persist session logs (like one opened in a private browsing window).

SSH keys are another option, but they require leaving a private key on the temporary laptop and adding a public key to your GitHub account—way less ideal for your "no personal info left behind" goal. The short-lived PAT is definitely the best fit here.

内容的提问来源于stack exchange，提问作者Saikat Saha