docs: recommend self-hosted runner with higher timeout for long scans

README.md

@@ -50,7 +50,7 @@ jobs:
 
 ### Job timeout
 
-A job gets 6 hours by default (`timeout-minutes` defaults to `360`), which is enough for Shannon.
+A job gets 6 hours by default (`timeout-minutes` defaults to `360`), which is enough for most scans. For larger repositories or slower model providers a scan can take longer than 6 hours; since GitHub-hosted runners are capped at 6 hours, a self-hosted runner is recommended for those.
 
 ## Examples
 

examples/pr-scan.yml

@@ -10,6 +10,10 @@ permissions:
 jobs:
   scan:
     runs-on: ubuntu-latest
+    # For larger repos or slower model providers, use a self-hosted runner (GitHub-hosted caps at 6h):
+    # https://docs.github.com/actions/hosting-your-own-runners/adding-self-hosted-runners
+    # runs-on: [self-hosted, linux]
+    # timeout-minutes: 720
     steps:
       - uses: actions/checkout@v4
 

examples/release-scan.yml

@@ -12,6 +12,10 @@ permissions:
 jobs:
   scan:
     runs-on: ubuntu-latest
+    # For larger repos or slower model providers, use a self-hosted runner (GitHub-hosted caps at 6h):
+    # https://docs.github.com/actions/hosting-your-own-runners/adding-self-hosted-runners
+    # runs-on: [self-hosted, linux]
+    # timeout-minutes: 720
     steps:
       - uses: actions/checkout@v4
 

examples/weekly-scan.yml

@@ -13,6 +13,10 @@ permissions:
 jobs:
   scan:
     runs-on: ubuntu-latest
+    # For larger repos or slower model providers, use a self-hosted runner (GitHub-hosted caps at 6h):
+    # https://docs.github.com/actions/hosting-your-own-runners/adding-self-hosted-runners
+    # runs-on: [self-hosted, linux]
+    # timeout-minutes: 720
     steps:
       - uses: actions/checkout@v4