How to properly merge requests in gitlab?

Question

git

Colleagues,
There are two branches in the private repository:

• master
  
• beta
  

In is masterforbidden (protected) git push, only merge.
CI / CD is configured for each of the branches equal to its environment.
Accordingly, we "bring" the branch betato the readiness of transferring it to production.
We do Merge Requestas a result of which a git commit is formed on master. Everything seems to be as it should be.
But I do not like that as a result Merge Requestthe branches are different and the same gitlab shows that it betastarts to lag behind mastereach git commitafter MR.
To do after merge from masterto betafor alignment - it seems dumb to me.
Tell me how to do it better, more efficiently, more correctly. Maybe not MR, maybe differently?

Answer 1

There is nothing wrong with falling behind the master. If you need fresh code from the master in a feature branch and don't want to litter the history with merge commits, use git rebase.