I started out in VS Code, so perhaps my experience is a little different. Here are the things that I found confusing …
- Because some items are untracked, there is a difference between the (local) repo and the (local) folder it is in.
BUT adding an existing file to .gitignore doesn’t make the file untracked. AFAIK, there is no way to make a tracked file untracked.
AND there is no way to create an untracked file on github, because there is no “save” button, just a “commit” button.
- I still find it confusing that I can log VS Code into github but I have to explicitly define a global user name and email.
2.5) When you create a new repo on github, it gives you a set of possible command sequences to link a local repo to the newly created github repo. These command sequences are wrong, since they do not include the step of defining a global name and email.
Most tutorials won’t help you (or to be precise, me) since they deal with the case of cloning an existing repo, not creating one on your local machine and pushing it to a new repo on github.com
The documentation for “git foo something something” is called “git-foo”, not “git foo”
4.1) The documentation for “git foo something something” will not distinguish the simple case – the caser you want – from every other case.
4.2) The documentation for “git foo something something” will use the term “refspec” Its meaning is ineffable.
4.3) If you get lost within the git man pages, you can find the way up at the bottom of the page.
Creating a profile page by creating a repo whose name is your user name is not as complicated as it sounds. In fact, it is not a tenth as complicated as it sounds.
AFAIK, there is no way in Markdown to refer to a file in another of your own repos except by using its full URL.
6.5) If my user name is dux and I have a repo foo containing a file some.txt, the url for the file is NOT github.com/dux/foo/some.txt
- AFAIK, there is no way to configure the “home page” of a repo so that someone sees the README first and not a pageful of commits.