path: root/doc/forum/Git_repo_updating
diff options
authorJoey Hess2016-03-04 12:31:10 -0400
committerJoey Hess2016-03-04 12:31:10 -0400
commit9f007eea3ac7487cca3c4bb662134023b19e5166 (patch)
tree91814825bea53cd1e1652d4957d7faf55f6d07f5 /doc/forum/Git_repo_updating
parent85bee039bf8b18ed103766c233edaa63a00c24fb (diff)
Diffstat (limited to 'doc/forum/Git_repo_updating')
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/Git_repo_updating/comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment b/doc/forum/Git_repo_updating/comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment
new file mode 100644
index 00000000..9aaa4f60
--- /dev/null
+++ b/doc/forum/Git_repo_updating/comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-03-04T16:25:55Z"
+ content="""
+You could certianly write a property that did a git pull every time. It
+would do some unnessesary work and still not keep the checkout always
+immediately up-to-date.
+Better to have some kind of hook that causes the checkout to update when
+changes are pushed into its parent repository. How such a hook works
+depends on where the parent repository is hosted. Propellor properties
+could be written to set up whatever's needed for such a hook on the system
+where the repository is checked out. If you're hosting your own git
+server as well, propellor properties could set up the post-update hook in
+the origin repo too.