Git + production and test server, how to test the work done and build a workflow?

Question

git

Hello!
It's time to start using version control for projects. I read good materials on git ( https://git-scm.com/book/ru/v1/ , https://habrahabr.ru/post/106912/) and got an idea about the optimal working model in git, but the practical skills are very not enough until I stumbled on how to link together an ide, a test server and a working one.
I really liked the model described on Habré - https://habrahabr.ru/post/106912/ , but the work of different branches with servers remained unclear to me.
For example: there are several people involved in the development of the site, they need to work in parallel, test it and, if the tests are successful, add it to the production server.
How to build such work? What do you need to have for this?
Correctly I understand: It is
necessary to have two servers, one test, another fighting. Set up all development branches on the test server, and is the master already uploaded to the production one?
How does the process itself work? The developer creates his own branch with dev, makes changes, but how then does he test them? He needs to upload them to the test server in dev so that he can later evaluate the performance of his solution, but then how can you maintain branches like Feature branches when it is not clear when they will be in the project? It turns out that such branches are not added to dev until necessary, but how then to evaluate their performance? Does every developer clone the project to their local machine and test it there? Do I need to deploy a virtual server like Open Server for this?
Put me on the right path, please))))
Development is planned to be carried out on phpStorm + Bitbucked.
I would be grateful if someone else could provide links to good materials on the topic of project management with git, how to build a workflow, how to make settings.
Thank you!

Answer 1

Read more about git flow. In fact, there is only one option.
Make a master branch - like a branch of the main production server. The second dev branch is the server branch for testing. then make a separate branch for each task. At the end of the work on the task, merge into the dev branch. After you have collected and tested a number of edits and tasks, you can merge master with the dev branch.

Answer 2

Путь истинный прост - работайте как угодно, заливайте веку main на живой и радуйтесь, по ходу дела моете добавить веток для отдельных тасков. Как настанет время магии сами поймете.

Answer 3

Почитайте про непрерывную интеграцию про Jenkins