source "$FEISTY_MEOW_SCRIPTS/core/launch_feisty_meow.sh"
source "$FEISTY_MEOW_SCRIPTS/tty/terminal_titler.sh"
-#hmmm: we need to dump all the outputs in this script into splitter
-
##############
# the maximum depth that the recursive functions will try to go below the starting directory.
test_or_die "git commit"
fi
-# # upload the files to the server so others can see them.
-# git push 2>&1 | grep -v "X11 forwarding request failed"
-# if [ ${PIPESTATUS[0]} -ne 0 ]; then false; fi
-# test_or_die "git push"
-
# a new set of steps we have to take to make sure the branch integrity is good.
- careful_git_update
+ do_careful_git_update
# we continue on to the push, even if there were no changes this time, because
# there could already be committed changes that haven't been pushed yet.
# upload any changes to the upstream repo so others can see them.
- git push 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
+ git push origin "$(my_branch_name)" 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
test_or_die "git push"
fi
restore_terminal_title
- true;
+ return 0
}
# shows the local changes in a repository.
restore_terminal_title
- true;
+ return 0
}
# reports any files that are not already known to the upstream repository.
restore_terminal_title
- true
+ return 0
}
# checks in all the folders in a specified list.
fi
}
+#hmmm: the below are git specific and should be named that way.
+
+function all_branch_names()
+{
+ echo "$(git branch -vv | cut -d ' ' -f2)"
+}
+
# a helpful method that reports the git branch for the current directory's
# git repository.
function my_branch_name()
{
- echo "$(git branch | grep '\*' | cut -d ' ' -f2)"
+ echo "$(git branch -vv | grep '\*' | cut -d ' ' -f2)"
}
#this had a -> in it at one point for not matching, didn't it?
# the git update process just gets more and more complex when you bring in
# branches, so we've moved this here to avoid having a ton of code in the
-# do_checkin method.
-function careful_git_update()
+# other methods.
+function do_careful_git_update()
{
-
local this_branch="$(my_branch_name)"
-#we want my branch here, don't we? not like parent or anything?
- check_branch_state "$this_branch"
- state=$?
- test_or_continue "branch state check"
- echo the branch state is $state
-#need to instead do something here if fails.
-# above is worse than useless code; in the situations i'm seeing fail, it reports no changes. *&@#*&@#
-
-echo DOING BRANCH WALKER
- # the above are just not enough. this code is now doing what i have to do when i repair the repo.
- local branch_list=$(git branch |grep -v '^\*')
+ # first update all our remote branches to their current state from the repos.
+ git remote update
+ test_or_die "git remote update"
+
+#appears to be useless; reports no changes when we need to know about remote changes that do exist:
+# check_branch_state "$this_branch"
+# state=$?
+# test_or_continue "branch state check"
+# echo the branch state is $state
+
+ # this code is now doing what i have to do when i repair the repo. and it seems to be good so far.
+ local branch_list=$(all_branch_names)
local bran
for bran in $branch_list; do
-echo GETTING LATEST ON: $bran
+# echo "synchronizing remote branch: $bran"
git checkout "$bran"
test_or_die "git checking out remote branch: $bran"
- git pull --no-ff
+ git pull --no-ff origin "$bran"
test_or_die "git pull of remote branch: $bran"
done
# now switch back to our branch.
git checkout "$this_branch"
test_or_die "git checking out our current branch: $this_branch"
-echo NOW REMOTE UPDATE
-
- # first update all our remote branches to their current state from the repos.
- git remote update
- test_or_die "git remote update"
-
-echo NOW THE FULL PULL
# now pull down any changes in our own origin in the repo, to stay in synch
# with any changes from others.
git pull --no-ff --all
test_or_die "git pulling all upstream"
-
-echo DONE CAREFUL UPDATE
-
- return 0
-
-# below has older shards of partial knowledge.
-
-# reslog=$(git log HEAD..origin/master --oneline)
-# if [[ "${reslog}" != "" ]] ; then
-# git merge origin/master
-
-# # from very helpful page:
-# # https://stackoverflow.com/questions/10312521/how-to-fetch-all-git-branches
-# for remote in $( git branch -r | grep -v -- '->' ); do
-# git branch --track ${remote#origin/} $remote 2>/dev/null
-##hmmm: ignoring errors from these, since they are continual.
-##hmmm: if we could find a way to not try to track with a local branch when there's already one present, that would be swell. it's probably simple.
-# done
-#
-##hmmm: well, one time it failed without the fetch. i hope that's because the fetch is actually needed and not because the whole approach is fubar.
-# git fetch --all 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
-# test_or_die "git fetch"
-#
-# git pull --all 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
-# test_or_die "git pull"
-
}
# gets the latest versions of the assets from the upstream repository.
elif [ -d ".git" ]; then
if test_writeable ".git"; then
$blatt
- git pull --no-ff origin 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
+ git pull --no-ff 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
if [ ${PIPESTATUS[0]} -ne 0 ]; then false; fi
test_or_die "git pull of origin without fast forwards"
fi
restore_terminal_title
- true
+ return 0
}
# gets all the updates for a list of folders under revision control.
save_terminal_title
+ local did_anything=
+
while read -u 3 dirname; do
- if [ -z "$dirname" ]; then continue; fi
+ if [ -z "$dirname" ]; then
+ # we often have blank lines in the input file for some reason.
+ continue
+ fi
+ did_anything=yes
pushd "$dirname" &>/dev/null
echo "[$(pwd)]"
$action .
popd &>/dev/null
done 3<"$tempfile"
+ if [ -z "$did_anything" ]; then
+ echo "There was nothing to do the action '$action' on."
+ fi
+
restore_terminal_title
rm $tempfile