How to deliver a project for testing, for production, and to hell?

Question

git

Good afternoon. I'm a big lammer git. Recently I felt that it is necessary to resolve conflicts locally with the help of an ide and not on a remote server on the console.

The structure is built as. Remote server, personal, for tests. Gitlab server which then pours on prod. And also a test one for testers, but so far they are not asking to pour it on it.

In general, the question is how do I use git to push to several places at once? For example, this is how I want to git push https://10.0.0.1 (address of the test server). git push origin master to gitlab server, etc. That is, I want to merge my changes to my test bench and check there, then merge to the main prod if everything is fine. And perhaps more is needed.
So far I'm using rsync for testing, but it's not convenient. I assume that git has built-in methods.

Answer 1

three branches in the git - dev, test and master
CI / CD
all local development is based on the dev branch as
soon as the feature is finished, we merge it into the test on the test server , when the feature is tested, we merge it into the master CI / CD is configured so that after a new push to the master, the code is laid out for production, we start the cycle in a new way