github - does git repo accumulate size when there is heavy branch which is deleted without merging back to master? -
i'm trying find efficient way temporarily add huge data files git repo without having make history grow , make overall repo bulky. need part of automated deployment i'm trying develop.
my solution, i'm trying validate is,
- on database server:
- generate data files deployment,
- create new branch,
- commit , push data files new branch,
- on deployment server:
- git clone new branch , download data files, and
- remove branch without merging master.
what i'm trying validate here is, if follow approach, repo relatively small, i'm not retaining branch, , never merging master? don't want repo accumulate large files history on time , make slow use repo. i'm trying reproduce scenario myself verify, because of latency issues, i'm not able validate actual size of repo. thoughts , suggestions appreciated.
the repo's size change due fact you're adding blobs @ point in repo's history. doesn't matter if you've merged master or not; fact these files reachable counts.
if want avoid adding large files repository significant burden, git-lfs store these larger binaries, bypass problem storing binaries somewhere else, referenced commit.
Comments
Post a Comment