How to organize version control for a production site and the developer's site?

So, is there a website, some mysite.ru, is tied to the appropriate repository. This is a working website that you can change/add/delete only if sure it is working.
There dev.mysite.ru that is what a clone mysite.ru with the only difference that there are no users and work with the code can be anything. Naturally, too, there is a remote repository, and under this website.
Now, the team of developers did something on dev.mysite.ru some new piece of the working, debugged, tested code.
As this code is placed on mysite.ru? Same in case if code is not added, and has changed or was deleted partially or completely.
Maybe I did not correctly understand the essence of git and I had something else to organize everything?
March 12th 20 at 08:01
2 answers
March 12th 20 at 08:03
Gitflow + restriction on merge to master, release branches + Jenkins
March 12th 20 at 08:05
You need to use GitFlow, here is the description of how it should work. (https://habr.com/post/106912/) we Also use samopisnye control panel in which in real time shows the status of all hosting accounts (development and Durga branches). If you want, contact, can show.

Find more questions by tags Git