I would like to ask you a question about the connection between visual studio 2022 and github.

I have never used Visual Studio 2022, so I have no idea about the phenomenon you reported or the cause. Just to give you a little bit of an opinion to solve the problem right now, the cleanest way to do it is to reverse the order of strong.

1. Create an empty repository in Github. For example, foo/bar.

2. I will clone it from the directory where the Ex01/ belongs to.
Open the power shell, navigate to the cd command to where the Ex01/ directory belongs, and type the commands below.

dir
# Try the above command first. Ex01 must be visible.

git clone https://github.com/foo/bar.git
# Use the command above to clone a remote git.
# "The term ""git"" is not recognized as cmdlet, function..." What if an error appears? There's no git. Install Git for Windows.
# I'll ask you to enter your user name and password, so please do it smoothly.

You will then see the bar/ directory next to the Ex01/ directory.
And in that directory, you'll find a hidden folder called .git.
(Very important; make sure this folder exists.)

2-9. Do you happen to have Ex01/.If the git/ directory exists, delete .

3. Move all files and folders in the Ex01/ directory to bar/.

4. Open the power shell and go to the bar/ directory with the cd command, and run the following:

git add . && git commit -m "first commit" && git push
# Stages all files, commits them roughly with any message, and then pushes them.
# I'll ask you to enter the password again, so please do it smoothly. Let's do advanced tasks such as registering SSH keys later.

5. Now forget Ex01/ and live with bar/. This is Github's new house and this is the new location of the project. If necessary, at this point, you can clear Ex01/ and then rename the bar/ directory to Ex01/.

Git is really easy to get what you started remotely, but I think it's really hard to upload something that you started locally remotely. SSH accessible remote locations should be set, which routes and which accounts are accessible should be identified, and configurations such as git config remote.origin.url should be set directly... I do. Maybe it's because some of the automated processes of those many tasks are twisted. But I don't know the details, and you don't have to be bothered by this from the beginning of the project, so I recommend you not to hold on to it too much, just go backwards and start at Github.com. I've rarely seen this fail.