How to organize version control for the production site and the development site?

Question

git

So, there is a site, some mysite.ru, the corresponding repository is attached to it. This is a working site, the code of which can be changed / added / removed only if you are sure of its performance.
There is dev.mysite.ru, which is still a clone of mysite.ru, with the only difference that there are no users there and you can do whatever you want with the code. Naturally, there is also a remote repository for this site.
Now, the development team has done something on dev.mysite.ru, some new piece of working, debugged, tested code.
How to put this code on mysite.ru? The same is true if the code was not added, but changed or was removed partially or even completely.
Perhaps I did not correctly understand the essence of the work of git and it was necessary to organize everything somehow differently?

Answer 1

Gitflow + limit on merge in master, release branches + Jenkins

Answer 2

You need to use GitFlow, here is a description of how it should work. ( https://habr.com/post/106912/) We also use a self-written control panel in which you can see the status of all hosting accounts (developer and other branches) in real time. If you want, contact me, I can show you.