Hi @simplesamples ,

No problem if you don’t understand it - we are here to help.

What exactly are you trying to achieve? If you’d just like to push (that is, I think, the most correct term to use) your local  master branch to the  master  branch on GitHub you could use the following command:

git push --set-upstream origin master

If the GH remote is called  origin (which it by default is), this will push your local  master  to the  master on GitHub. You do need to execute this command manually, but after that automatically pushing using VS or VS Code should work fine without any manual actions from your side.

Let us know if you get more errors or need additional assistance!

Thank you, Mark.

When I use a command prompt and go to the repository’s path and issue that command I get:

fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights

and the repository exists.

So I am not sure what is happening. Since I am not experienced with the use of the command line, I am not sure where the credentials are coming from. I tried to figure that out and just doing that makes my head spin; there are so many ways to specify credentials. Well I think that since I use Visual Studio I should assume I am using whatever it uses. Anyway, to attempt to learn things I tried the following.

G:\Sam\Documents\Source\Repos>git config -l --global
user.name=Sam Hobbs
user.email=SimpleSamples@users.noreply.github.com
gui.recentrepo=C:/Users/Sam/source/repos
filter.lfs.clean=git-lfs clean -- %f
filter.lfs.smudge=git-lfs smudge -- %f
filter.lfs.process=git-lfs filter-process
filter.lfs.required=true
credential.helper=manager

And that is very interesting. The most interesting part is the recentrepo. Windows allows us to specify a different partition for our “Documents” folder but it does not support it very well. Ugh! The relevant repository is in my G: (as shown in the preceding) but the preceding says C: for the recentrepo. So that is a likely problem. Right? Does that provide enough for you to suggest what to try next?

Hi @simplesamples ,

Can you post the output of  git remote -v when inside the repository here? Thanks!

Please check the output for sensitive information, and if so, censor it!

I get nothing. I tried using both Git Bash and a Windows command prompt. Both produced no output, not even an error message.

I did that in the folder that has a .git directory; it has about eight projects in it.

So just to see if I could get that to work I went to my local repository for First Heroku Site. There is not much there but the output of the specified command is:

origin https://github.com/SamHobbsOrg/HerokuFirst.git (fetch)
origin https://github.com/SamHobbsOrg/HerokuFirst.git (push)

@simplesamples  it is correct if Git then returns an empty response - it simply means you don’t have any remotes 

You simply need to add your own Git repository as a remote (using this article: https://help.github.com/en/articles/adding-a-remote) and then you can retry the command mentioned earlier.

Thank you @mpboom. I think I am making progress. After adding the remote I tried the push again and I get:

G:\Sam\Documents\Source\Repos>git push --set-upstream origin master
git: 'credential---help' is not a git command. See 'git --help'.
To https://github.com/SimpleSamples/Repos.git
 ! [rejected] master -> master (fetch first)
error: failed to push some refs to 'https://github.com/SimpleSamples/Repos.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

I think the part about credential—help is my mistake resulting from my attempt to figure things out. I hope it is doing nothing except produce that warning. As ar as you do not have locally that gets back to my original post, I did delete a project that I know I should not have. I deleted it both in my local and remote repositories but I should have known that Git has data about things like that. So I need to clean up what is in the remote.

Would it work to just create a new remote? I have everything locally. Can I first rename the existing remote? Or I should delete the remote but if nothing else I do not mind using a different name.

I posted a reply but then I edited it a couple of times then it needed approval but I think now it is gone. I apologize if the following is a duplicate.

Thank you @mpboom. I think I am making progress. After adding the remote I tried the push again and I got:

G:\Sam\Documents\Source\Repos>git push --set-upstream origin master
git: 'credential---help' is not a git command. See 'git --help'.
To https://github.com/SimpleSamples/Repos.git
! [rejected] master -> master (fetch first)
error: failed to push some refs to 'https://github.com/SimpleSamples/Repos.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

I think the part about credential—help is my mistake resulting from my attempt to figure things out. I hope it is doing nothing except produce that warning. As far as you do not have locally that gets back to my original post, I did delete a project that I know I should not have. I deleted it both in my local and remote repositories but I should have known that Git has data about things like that. So I need to clean up what is in the remote.

Would it work to just create a new remote? I have everything locally. Can I first rename the existing remote? Or I can delete the remote but if nothing else I do not mind using a different name.

Hopefully this is just a progress report. I am getting:

fatal: refusing to merge unrelated histories

If that is expected for the situation described previously then I should be able to proceed with the merge and such.

Thank you. I think it is fixed.

I used:

git pull --allow-unrelated-histories

as in Solved: How to deal with "refusing to merge unrelated hist… - GitHub Community Forum. Then I did the push and now everything seems to be (“uploaded”) pushed. I do try to use proper terminology but in this situation I decided to use common terminology because some people really do not appreciate use of the wrong terminology.

That is great news, thank you for sharing your journey with the community @simplesamples !