Different themes in one issue AND/OR branch creates confusions

[jojo12]

After all for testing, it would be better to have each theme separated in issue and in branches.
Actually, we have changes which overlap eachother.
If possible, please try to separate. Thanks

[mckillo]

When we are making small changes or additions, a branch is not necessary and an issue-commit is sufficient.

For the new or review features, in that case, it is always better to open a branch.

In the recent case of a recurrence review, I opened a branch, but other issues have been opened that depend on the changes and improvements of that review (mixing cases |1744 and #1764, nothing serious). In this case, all issues should be included in the same branch, it could be divided into several child branches, but it is unnecessarily complicated to manage with GitHub, especially when it is a developer who makes the revision changes.

If there are several developers working on a feature or revision, in that case always one branch and each issue in a child branch with its commits.

Opening many branches is not good, as it will generate conflict when there is no communication, by touching commits on the same files. Everything has its pros and cons. I suppose that in each case, we are applying branches and commits, it hasn't been so bad for us this time :-)