Your comments

Integrations with tools like atlassian bitbucket/jira helps creating prefixes to group branches based on usual '/' depending on the task type (feature, bug, ...), the problem comes when multiple users need personal branches, in this case to avoid first level folders floading it is be helpful to nest these branches as "personal" but SmartGit doen't handle a second level of folders

Yes, I meant rendering only (here is a reference: https://en.wikipedia.org/wiki/Markdown and here https://github.com/microsoft/vscode an example of the readme.md shown below the code).I like having this kind of quickly available documentation rather then relying on external tools...