honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build(publish.sh): do not error when tmp/code.angularjs.org already exists 

I'm not sure what's the best way to update the shallow repo and I'm in a state where there is nothing to be
updated so I'll revisit the proper fix the next time I'm doing a release unless someone beats me to it.

Closes #5872
This commit is contained in:
Igor Minar 2015-12-13 15:47:46 -08:00 committed by Igor Minar
parent e891baeea4
commit d3a79db48d
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
tools/code.angularjs.org/publish.sh
View File

@ -26,8 +26,23 @@ function init {
function prepare { function prepare {
echo "-- Cloning code.angularjs.org"
git clone git@github.com:angular/code.angularjs.org.git $REPO_DIR --depth=1
if [ -d "$REPO_DIR" ]; then
# TODO(i): it's not clear how to safely fetch and update a shallow clone
# I'll need to test this during the next release
echo "-- TODO: Update code.angularjs.org repo at $REPO_DIR"
echo "-- TODO: if pushing the 'publish' action fails, rebase the repo manually and push"
echo "-- TODO: or delete $REPO_DIR and rerun the prepare and publish steps"
#cd $REPO_DIR
#git fetch --update-shallow origin
#git checkout master
#git merge --ff-only origin/master
#cd -
else
echo "-- Cloning code.angularjs.org into $REPO_DIR"
git clone git@github.com:angular/code.angularjs.org.git $REPO_DIR --depth=1
fi
echo "-- Updating code.angularjs.org" echo "-- Updating code.angularjs.org"