rationalizing repository downstream flow control

[feisty_meow.git] / scripts / rev_control / push_repo_downstream.sh

diff --git a/scripts/rev_control/push_repo_downstream.sh b/scripts/rev_control/push_repo_downstream.sh
new file mode 100644 (file)
index 0000000..de455a8
--- /dev/null
+++ b/scripts/rev_control/push_repo_downstream.sh
@@ -0,0 +1,46 @@
+#!/bin/bash
+
+# this script works on a specialized type of git checkout that has been configured
+# to push to a "downstream" repository, while still pulling from its normal origin.
+# the downstream destination might be a github or sourceforge repository that is
+# loaded from a personal repository or server.
+#
+# to set up the repository for relaying downstream, just do the normal checkout
+# or clone on it from the real origin.  for example:
+#
+# $ git clone git://feistymeow.org/feisty_meow
+#
+# and then add the downstream remote repository:
+#
+# $ git remote add downstream https://github.com/fredhamster/feisty_meow.git
+#
+# once the repository has been created, you can synch all updates that
+# have been checked into the origin repository with the downstream version
+# by running this command:
+#
+# push_repo_downstream ~/relay_repo_folder
+
+#hmmm: make this support multiple dirs?
+
+dir="$1"; shift
+if [ -z "$dir" ]; then
+  dir=.
+fi
+
+pushd "$dir"
+
+# get everything from the origin.
+git pull
+
+# get everything from the origin.
+git pull
+
+# turn off occasionally troublesome setting before checkin.
+unset GIT_SSH
+
+# send the little boat down the stream to the dependent repository.
+git push origin master <"$PASSWORD_FILE"
+
+popd
+
+