summaryrefslogtreecommitdiff
path: root/doc/forum/Git_repo_updating/comment_1_f601e29b5fb82700b21914f3fb1ef49b._comment
blob: 9aaa4f60d544e5bc9a26423f332bcce951a42fa4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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.
"""]]