How to organize development with GIT if there are many tasks, each on its own branch, and all of them must be available on the test site at any time?

Question

git

There is a personal test server my.dev.local on a remote machine.
There are a number of tasks that are periodically updated.
All these improvements should always be available when entering the test site for the customer.
When using GIT branches, switching to a branch of a task, we lose changes from other tasks, i.e. these improvements disappear from the site. There are dozens of such switches from task to task per day.
Tell me how to organize work using GIT in such conditions?

Answer 1

You can deploy all branches to different addresses.

Answer 2

What method do you use to work? Git flow or something like that?
Merge everything tested into master, or into preview, as suggested by 183614956 , or into some other branch.

Answer 3

use gitflow