Home/ Questions/Q 8390917
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T19:07:26+00:00

I have a script which emails me a reminder if I’ve forgotten to commit

  • 0

I have a script which emails me a reminder if I’ve forgotten to commit or push some code on each of my 40+ repositories.

With 2 of my projects, I have followed the answers in these posts, where I have set-up “git-push” to push to multiple repositories:

pull/push from multiple remote locations

git push to multiple repositories simultaneously

So I have a .git/config file with:

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
[branch "master"]
    remote = origin
    merge = refs/heads/master
[remote "origin"]
    url = https://www.example.com/git/project/
    url = git@github.com:username/project.git
[remote "example"]
    url = https://www.example.com/git/project/
    fetch = +refs/heads/*:refs/remotes/example/*
[remote "github"]
    url = git@github.com:username/project.git
    fetch = +refs/heads/*:refs/remotes/github/*

This works well when it comes to doing a git push/pull.

With the script I have used:

git status --short

But this only shows un-commited changes… even without the “–short” flag, it does not show what normally appears with only 1 remote:

Your branch is ahead of 'origin/master' by 1 commit.

Trying to run any of the following “diff” commands also doesn’t seem to work… well it does on the first time, but it seems to remember the remote files at the date/time when it was setup, so as you make more changes it compares them against that version in history:

git diff --name-status "origin";
git diff --name-status "origin/master";
git diff --name-status "example/master";
git diff --name-status "github/master";

Any thoughts? I am fairly new to Git.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I believe this method is possibly a bit buggy, as it seems to remember a commit ref for each remote, but this does not get updated when doing a push/pull… so when checking via a diff, its always going to look at the old commit ref for a comparison.

    While its not a solution to this setup, I have gone back to a single remote setup, but edited it so that it has 2 urls… so while the pull only happens from one remote, when I push, it goes to two:

    [core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
[branch "master"]
    remote = origin
    merge = refs/heads/master
[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    url = https://www.example.com/git/project/
    url = git@github.com:username/project.git

    Note: This only works for now, as I’m the only committer.

    • 0