-
-
Save c0ldlimit/4089101 to your computer and use it in GitHub Desktop.
# Create a new repository on the command line | |
touch README.md | |
git init | |
git add README.md | |
git commit -m "first commit" | |
git remote add origin https://github.com/c0ldlimit/vimcolors.git | |
git push -u origin master | |
# Push an existing repository from the command line | |
git remote add origin https://github.com/c0ldlimit/vimcolors.git | |
git push -u origin master |
this should help github documentaion
you need to install “gh”, the doc has explained it pretty well.
But doesn't this add an extra 'master' branch instead of pushing to 'main' branch?
But doesn't this add an extra 'master' branch instead of pushing to 'main' branch?
No.
git push -u origin master
is nowgit push -u origin main
Thanks. Commentary or links on why this change was made would be helpful.
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.
This happened when i tried " git push -u origin main " from my terminal on my PCTip, using
git push -u origin HEAD
automates the command to use whichever local branch you're currently in. Also yeah, it's what the error says.For developers, if you are using a password to authenticate Git operations with GitHub.com today, you must begin using a personal access token over HTTPS (recommended) or SSH key by August 13, 2021, to avoid disruption. If you receive a warning that you are using an outdated third-party integration, you should update your client to the latest version.
You need to create and use a PAT as stated and linked in the article.
I'm a developer. I am trying to do a git push for the first time in several years and am curious to see if this is going to be a blocker for me.
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.
This happened when i tried " git push -u origin main " from my terminal on my PC
Thanks! The date was helpful.
@codewizard13 in reference to the default branch name change, it remains a controversial topic, but here is a fairly unopinionated synopsis.
Thanks! Worked like a charm. Tried many other suggestions before this one. Thanks again.
I have a question, we need to create a repo on github first, then only we can push our repo? Can we not directly push a repo to our profile and it creates the repo from the folder name?
Just one note: if the repository doesn't exist in Github, first you will have to create it: https://help.github.com/articles/creating-a-new-repository/
i saw that vs code does it for you without us having to go to github to create one first
Alternatively, if you prefer to do this stuff from your CLI, you can install github for your terminal and then is as simple as typing:
gh repo create your_repo
Hello, The command 'gh repo create your_repo' is showing invalid
GitHub Licenses API?
It's not a CLI proper but has a lot of potential for getting the license data into the terminal.