Git - Everyone Pushing to Same Branch in Different Files
This is not a "strategy". This is a sure way toward chaos.

The idea behind "trunk branch", which means having one branch for integration, does not mean that everyone should be pushing their changes to this branch directly. It only means that his branch is the place where integration happens.

Why do you even need two branches, Release and Master? What benefit does this bring? Probably just the benefit of confusing git history into an incomprehensible mess so that no one knows what is happening.

Stop this madness!


Make each change on its own pull-request branch (call it feature branches if you like).
Make sure that these pull-requests are not merged into the main integration branch before the code there goes through some minimal code-review.
Restrict from pushing directly to your integration branch.
For cleaner history, make sure that the pull-request branch if first rebased on top of integration.
Make sure that merges of pull-requests are not fast-forwarded and clearly visible in history.


The above will allow for several benefits,


Higher quality and less "human error" mistakes.
Learning and teaching each other cool dba tricks (during code reviews).
Keeping the integration branch green most of the time (it works!).
High trust that you are not shooting yourself in the leg using your process.
Way less "oops, I overwrote your change" kind of merges.
High trust that new team members are not going to mess things up.
Git history that is a thing of beauty and a joy forever.


And more ...

Prettier explanation of the "Feature Branch Workflow" is available on the Atlassian Git website here https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow