summaryrefslogtreecommitdiff
path: root/doc/forum/Git_repo_updating.mdwn
diff options
context:
space:
mode:
authormithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a822016-03-04 15:44:43 +0000
committeradmin2016-03-04 15:44:43 +0000
commit85bee039bf8b18ed103766c233edaa63a00c24fb (patch)
tree305a9c09f61eebe1a943573790b5c8e8767ec0da /doc/forum/Git_repo_updating.mdwn
parent397301d9a520b719c112b6634370ed66ace09a61 (diff)
Diffstat (limited to 'doc/forum/Git_repo_updating.mdwn')
-rw-r--r--doc/forum/Git_repo_updating.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/Git_repo_updating.mdwn b/doc/forum/Git_repo_updating.mdwn
new file mode 100644
index 00000000..e0cccedd
--- /dev/null
+++ b/doc/forum/Git_repo_updating.mdwn
@@ -0,0 +1 @@
+Propellor.Property.Git.cloned clones a git repo to a location, great! Is there an easy way to keep it updated afterwards, though? I guess having a property that enforce up-to-dateness wouldn't be so practical since you have to hit the remote to check, perhaps a cron job to run some equivalent of `git fetch && git reset --hard && git clean -dfx`. (Just thinking out loud here, and wondering what everyone else is doing)