"Git Workflow for Humans"
"optimized for workflow simplicity"
"branch workflows are dead simple"
"Nice and simple – the way it should be"
As Legit is now described at www.git-legit.org, what would suggest to beginners that it's anything but the answer to their prayers?
I suppose if they squashed commits that weren't there's, then that's a problem of course. But just rebasing their own work between branches?
The real trouble I'd see for this mythical newbie is when they get in a situation that calls (correctly) for a force push. That would come-up if they fork an OSS repo, push some changes to their fork, then do a $ git pull --rebase from the OSS repo to bring in new changes.
When they go to push again to their fork, they will get an error that will require a force push. The force push will be fine because they are working alone, but it could cause an issue for a new git user.
But I'm a little unsure of what trouble you're afraid the maintainer would have.
"Once you're ready to share your commits, or pull in remote commits — just press the Sync Branch button. We'll perform a smarter version of pull --rebase && push that reduces merge commits but doesn't rewrite your merges."
from the first paragraph on the page:
"Legit is a complementary command-line interface for Git, optimized for workflow simplicity. It is heavily inspired by GitHub for Mac."