What is the best way to post releases when working with the git flow model?

Question

PHP

I have a php project.
Now, when a task appears, the developer creates a new branch and does his task there.
Then it is merged into the develop branch, checked and only then merged into master.
The problem is that when a lot of completed tasks accumulate in develop, they all merge into master in a batch and this is not very convenient.
Is there some kind of web interface for sorting out all this, so as not to sit in the source tree to watch which files from where and where?

Answer 1

How about merging into master not a bunch, but each branch separately?

Answer 2

I won’t say anything about the interface... probably any git manager that draws a network of commits in the form of a tree / graph will do
, but about releases and problems with understanding what came from - so that there are fewer commits and the history is clearer - you can try using --squash when merging features in dev - then you will have one commit for each completed feature.