Does git push always return an error to "if [ $? -ne 0 ]" when the push
fails? Is this sufficient to verify your git-push worked? I'm being
asked to advise on commands to 'verify the canonical repo is in good
working order' immediately before a push and immediately after a push
(for total automation). I'm used to doing pushes manually. I think
git-push itself will tell you if there's a problem, and there's no need
for 'before' and 'after' checks. Correct?
Very Limited Scope of Context:
We don't do anything special in the push. We are just fast-forwarding
the master branch and there is only one branch (master). (The
powers-that-be are doing their own change control (ie, file locking) and
only care to copy files to the worktree of master, git-add, git-commit,
and git-push to canonical.) They have created a change control menu
that only uses git to 'check out' source and to 'commit source'
automatically via scripts. They are doing the merges manually and not
using git for that so there is no 'merging of master' going on as far as
git is concerned. They're basically using git to replace cvs in their
legacy change control so they don't wish to use any git functionality
like branches, merges, etc, at this time. I think they are just using
git checkout, git add, git commit, to say they have put the changes into
a 'change control repository'.
v/r,
neal
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html