Do I understand all the steps of project preparation correctly?

Question

Work organization

Hello everyone, before that I made edits directly on the prod versions of projects, this is due to the fact that all the projects I work with are not very visited, and plus the fact that I studied almost on my own and I don’t know a good example, now I want to start doing everything humanly)
So there is a working project, I created a copy of it on the subdomain, so to speak, stage, now I want to set up the environment and version system (I also used only sublime with notepad ++ for ftp before), now I’m moving over to visual studio code, so far for a test time, while I understand that, yes, how I chose bitbucket, it has a free private repository compared to github,
1) in order for me to set it all up, I need to download everything from the server to the LAN, add the project to vsc, synchronize the LAN with the server (I chose this addition liximomo.sftp), install git and upload all the files to the bitbucket repository, I understood everything correctly ?,
2) do I understand correctly that we need to work like this - we make edits on the local area, then upload the changes via ftp if everything is fine, then at the end of the work we do push / if something does not suit us, we can roll back the necessary changes to the local area through the repository and then upload it to the site again via ftp?
3) I have the whole project with photos, etc. weighs 5.5GB, I see bitbucket gives 1GB for free, I need to upload only files with code to the repository, i.e. everything except photos, and let the photos be outside the repository?
4) well, if you can write what plugin do you use for ftp in vsc ?, as I wrote, I almost always worked with ftp in notepad and got used to it, you don’t need to download anything, etc. I connected, did what I needed and forgot, so far I can’t find such a
Ps I apologize right away if the questions are too primitive, there’s just no one to ask for real advice)

Answer 1

In the last project where I worked, it was like this:
Everyone works in their own local area or on their own server. Each task was done in a separate branch, after which a pull request was created in the dev branch.
If the team leader after the review agreed to merge the branch, then the branch was merged into dev.
The dev branch was automatically taken (git pull) from the github and displayed on the staging server.
If everything was OK after the staging test, then the branch was sent to production (to another server) and this was done by draining the dev branch into master, i.e. the production server automatically pulled the master branch
how to do the same? Pretty easy.
1. You need to create your own git repository, for example, on github.
2. Raise the staging server (for pre-release and testing) and do git pull origin dev by cron, for example, once every 10 minutes
3. Also on the production server by cron do git pull origin master
Merge branches manually after each pull request to dev or testing in master and then push to github.
I don't know if I explained it clearly, if so, ask.