git-arr: increase default 'max_pages' value

The 'max_pages' default value of 5 is quite low. Coupled with
'commits_per_page' default 50, this allows for only 250 commits, which
is likely unsuitable for even relatively small projects. Options are to
remove the cap altogether or to raise the default limit. At this time,
choose the latter, which should be friendlier to larger projects, in
general, while still guarding against run-away storage space
consumption.

Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Alberto Bertogli <albertito@blitiri.com.ar>

2 files changed, 3 insertions, 3 deletions

diff --git a/git-arr b/git-arr
index 5a650ee..f559af4 100755
--- a/git-arr
+++ b/git-arr
@@ -51,7 +51,7 @@ def load_config(path):
         'recursive': 'no',
         'commits_in_summary': '10',
         'commits_per_page': '50',
-        'max_pages': '5',
+        'max_pages': '250',
         'web_url': '',
         'web_url_file': 'web_url',
         'git_url': '',
diff --git a/sample.conf b/sample.conf
index f5e950a..fb8bbdd 100644
--- a/sample.conf
+++ b/sample.conf
@@ -29,8 +29,8 @@ path = /srv/git/repo/
 # Maximum number of per-branch pages for static generation (optional).
 # When generating static html, this is the maximum number of pages we will
 # generate for each branch's commit listings. Zero (0) means unlimited.
-# Default: 5
-#max_pages = 5
+# Default: 250
+#max_pages = 250
 
 # Project website (optional).
 # URL to the project's website. %(name)s will be replaced with the current