I'm not sure who your target end-user is, but I think the focus on "git" both in your branding and explanation leads people to focus on that aspect rather than the (great) idea of having easy-to-use revision management for digital assets. How that's implemented (in this case, git) is irrelevant to a marketing manager or a creative who is supplying the content.

If developers are a large part of who you see as your end user, then sure, keep as is. But if they're not, I'd consider re-evaluating the use of git as your main selling point and highlight the "history tracking" aspect of the product.