Unified · Split
| @@ -26,3 +26,16 @@ the .git directory. · 25 unmodified lines | ||
| 26 | 26 | A less likely cause is that the repo is, infact, not a valid repo. Try |
| 27 | 27 | to run 'git show' in the offending repo to see if git also thinks your |
| 28 | 28 | repo has issues. |
| 29 | + | |
| 30 | + | |
| 31 | +### Why is the idle time for my repository wrong? | |
| 32 | + | |
| 33 | +By default CGit uses the modification time of the default branch's ref | |
| 34 | +file as a quick method of determining when the repository was last | |
| 35 | +changed. If you primarily work on other branches then this work will | |
| 36 | +not be reflected in the idle time. | |
| 37 | + | |
| 38 | +You can use a post-receive hook to run a script that tells CGit the | |
| 39 | +correct modification time by writing to ``info/web/last-modified``. An | |
| 40 | +example is provided in the CGit repository at | |
| 41 | +``contrib/hooks/post-receive.agefile``. | |