ci: Make the max number of commits tested explicit
What changed, and why it matters
This commit only renames a GitHub Actions CI job and adds a comment to make clear that the workflow tests a maximum of 6 ancestor commits. There is no code, build, or runtime change, and no security issue is introduced or fixed.
No action required; this is a non-functional CI labeling change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is purely cosmetic/documentation in .github/workflows/ci.yml. The job name changes from ‘test each commit’ to ‘test max 6 ancestor commits’, and a comment is added next to the existing MAX_COUNT: 6 variable. The behavior, fetch depth calculation, and timeout remain identical.
Changed components
.github/workflows/ci.ymlInspect captured patch +2 / −2
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 0265583b..2f57f8c9 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -56,12 +56,12 @@ jobs:
fi
test-each-commit:
- name: 'test each commit'
+ name: 'test max 6 ancestor commits'
runs-on: ubuntu-24.04
if: github.event_name == 'pull_request' && github.event.pull_request.commits != 1
timeout-minutes: 360 # Use maximum time, see https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes. Assuming a worst case time of 1 hour per commit, this leads to a --max-count=6 below.
env:
- MAX_COUNT: 6
+ MAX_COUNT: 6 # Keep in sync with name above
steps:
- name: Determine fetch depth
run: echo "FETCH_DEPTH=$((${{ github.event.pull_request.commits }} + 2))" >> "$GITHUB_ENV"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.