Are there options for organizing work with git branches for the manager?

Question

git

Hello.
The situation is as follows: there is a project on which I am working, I am a programmer, a manager, and there is also a customer. It often happens that 2 tasks, having arrived for execution, affect the same component of the system. It is most convenient to make a separate branch for a separate task, which I do. After working on the task, making a commit and switching the branch:
1. files from the first branch remain on the server, and if I start editing the files, errors are possible and I will have to merge into the first branch into the second.
2. it is likely that as a result one of the tasks can be canceled and will not go into production, and because of this, you have to roll back everything until the moment the branches are created, transfer the code in pieces.
3. Tasks in general can conflict with each other and they will have to be done in different branches, and then only one will be poured into the master century.
I hope everything is clear here.
Therefore, the question arises, is it possible to somehow organize switching between the branches of the manager and the customer through some interface in such a way that the branch changes on the server and they can test tasks independently of each other.

Answer 1

It is possible and necessary.
Just upload different branches to different showroom servers.

Answer 2

It is undesirable to let managers and other humanitarians into the git. Maximum - so that bugs can be registered, but only BY THE TEMPLATE and not just "it doesn't work for me, sort it out, cattle") Let the rest of managerial shit boil in 1C and other trackers that are not related to the product.

Answer 3

The manager and the customer do not have access to write to the git
Tasks are set through the issue/task tracker
Deploy - automated and isolated. The manager/customer says which branch he wants to see. You start the script and it gets a sandboxed version to work
with. No changes are made to the code on the test server. He is killed along with the DB