fix: make commit steps continue-on-error for branch protection (#122)
When branch protection prevents direct pushes from GITHUB_TOKEN, the workflow should still succeed since artifacts carry data between jobs. The git commits are for long-term persistence only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Juan Manuel Servera committed
May 19, 2026 at 17:39 UTC
942cc1e4f009bb4c9a0912696e020c7af3f5c20c
1 file changed
+3
.github/workflows/crawl-and-publish.yml
+3
@@ -117,6 +117,7 @@ jobs:
117
if-no-files-found: warn
118
119
- name: Commit crawl data
120
+ continue-on-error: true
121
env:
122
DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
123
run: |
@@ -299,6 +300,7 @@ jobs:
300
--source "$ANALYSIS_SOURCE"
301
302
- name: Commit analysis
303
+ continue-on-error: true
304
env:
305
DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
306
WEEK: ${{ steps.analysis-context.outputs.week }}
@@ -378,6 +380,7 @@ jobs:
380
run: python3 scripts/generate_rollups.py
381
382
- name: Commit generated content
383
+ continue-on-error: true
384
env:
385
DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
386
WEEK: ${{ needs.analyze.outputs.week }}