Make sure them "git Push"

Personally I dont run into this problem;
But people I interact with definately do

                               they know they do.

Sometimes I am waiting for changes that they never pushed.
For all the programmers who like to commit locally and never push.
With LOVE this is made for you. #made #with #love #or-atleast-noble-intentions.

Why, per user request, but also it seems a good use of a daemon.

ASK: "You made a supervisor program(daemon) background process that monitored another background process(daemon) ... (jokingly) If only there was a program that pushed my commits before shutting down my computer."

Me: "Actually, achievable/doable, what operating system? Ive done for a mac, linux should be strait forward."
ASK: "Windows operating system"
Me: "windows... ouch . I will have to take a look!"

Daemon process to monitor for shutdown ... keep computer alive until resolved.
First Pass: Search all git projects on computer for commits ready to be pushed.
Ignore files that have staged or have not yet been staged.
Second Pass: How does the programmer want to interact with unstagged/stagged commit's with no commit message.
Second Pass will take up time. Possibly they are a git add -p.
Possibly automated blunt(not recommend) or possibly ignore.

Requirements

sooo... sadly it has to be windows.
You have been waiting, and now I will have to learn a windows thing.
Meaning possible future windows support of my other applications, after this project.

This is a good initial step. More to come.