Your comments
That's interesting. They write "Consider starting the commit message with an applicable emoji" ... so this is about some more formalized classification of the commit. I'm not sure whether I would like to see all that different symbols in the Log graph, but being able to quickly distinguish between e.g. feature improvements, performance improvements, bugs and refactorings sounds really useful to me.
Can you give a sample repository URL of a project which is using GitMojis? I'm wonder whether they could somehow be used in the Log graph ...
> When you pick the "permanent option", the index (clean) does not appear when the Working Tree has changes. But it will appear when both are clean.
That's actually unexpected. For me, "Index (clean)" will always show up, regardless of the working tree state. If you can provide a small test repository for which the problem is reproducible, that would be great.
> Shouldn't this be set as the default when switching to Working Tree as main Window?
I don't think it's more reasonable to use this as default. It's simply a matter of taste.
> In Permanent mode and Working Tree clean, I think the index should show only 'on demand'. Maybe this is a bug?
Either everything on demand or everything permanent is reasonable to me. So again, a matter of taste. If you want to have a third mode or a corresponding low-level property, please create a new topic.
From the Commits view hamburger menu, you can select to Show Working Tree & Index Permanently.
To get a better idea on different requirements, I have added another issue for filtering graphs for sub-directories: https://smartgit.userecho.com/communities/1/topics/879
You can switch off the working tree display in the Log graph in the Preferences, Low-level Properties, log.workingTreeState.
No, it's not planned for 18.2.
Will become a valid option (not experimental) in 19.1
Customer support service by UserEcho
Why don't you ignore unversioned files? You may even ignore them only for you in .git/info/exclude