From 9f007eea3ac7487cca3c4bb662134023b19e5166 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 4 Mar 2016 12:31:10 -0400 Subject: comment --- .../comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/Git_repo_updating/comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment (limited to 'doc/forum/Git_repo_updating') 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. +"""]] -- cgit v1.2.3