We have a repository that can have over a hundred commits a day. Sourcetree doesn't seem able to handle this though and loading the repository takes over 15 minutes, are there some methods we can implement to help improve this loading time?
Hi @Ahmad Sidawi
Commit volume is rarely the real cause. It is usually the number of refs Sourcetree has to draw plus file status polling.
What I would try:
git remote prune origin.
git gc
git commit-graph write --reachable --changed-paths
Option labels shift between Sourcetree versions, so you might check yours first.
This thread is old now, so did anything help in the end?
Cheers, Martin
It looks like you're new here. Sign in or register to get started.
