• Remove max-parallel limit to allow docs jobs to run concurrently
• Add concurrency control to prevent race conditions during commits
• Simplify git push retry logic with shell conditional operator
• Consolidate git setup and commit steps into single operation

Remove parallelization limit from docs job

• Removed max-parallel: 1 constraint from documentation job matrix
• Allows multiple language documentation builds to execute in parallel

.github/workflows/release.yml

Add concurrency control and simplify commit logic

• Added concurrency group gh-pages-write with cancel-in-progress: false to prevent concurrent
 writes
• Consolidated git setup and commit steps into single step
• Simplified push retry logic by replacing loop with shell conditional operator
• Removed manual retry loop with sleep delays

.github/workflows/update-documentation.yml

Description

commit-docs now does a single git push origin gh-pages without git pull --rebase/retry, so if
gh-pages is updated out-of-band after checkout (e.g., a manual hotfix commit), the push will be
rejected as non-fast-forward and docs won’t publish.

Code

.github/workflows/update-documentation.yml[R102-110]

+      - name: Commit documentation
        run: |
          git config --local user.email "selenium-ci@users.noreply.github.com"
          git config --local user.name "Selenium CI Bot"
-      - name: Commit documentation
-        run: |
          git add docs/api/
-          if git diff --staged --quiet; then
-            echo "No documentation changes to commit"
-          else
+          git diff --staged --quiet || {
            git commit -m "Update ${{ needs.parse.outputs.language }} documentation for Selenium ${{ needs.parse.outputs.version }}"
-            for _ in 1 2; do
-              git pull --rebase origin gh-pages && git push origin gh-pages && exit 0
-              sleep 2
-            done
-            exit 1
-          fi
+            git push origin gh-pages
+          }

Evidence

The updated workflow checks out gh-pages and then pushes directly, but the previous logic that
rebased/pulled and retried pushes was removed. This reduces resilience to any external gh-pages
updates not coordinated by this workflow’s concurrency gate.

.github/workflows/update-documentation.yml[92-110]
.github/workflows/release.yml[141-160]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`commit-docs` pushes to `gh-pages` without rebasing/pulling or retrying. If `gh-pages` advances after the checkout step (e.g., manual commit/hotfix), `git push` can fail with a non-fast-forward error and the docs update will be lost.

### Issue Context
This PR intentionally parallelizes language doc generation and serializes writes via a concurrency group, which prevents *internal* simultaneous writers. However, removing the pull/rebase+retry logic makes the job fragile to any *out-of-band* `gh-pages` updates.

### Fix Focus Areas
- .github/workflows/update-documentation.yml[92-110]

### Suggested change
Reintroduce a pre-push sync step (and optionally a small retry), e.g.:
- `git pull --rebase origin gh-pages` immediately before `git push`
- optionally retry on push failure with a short backoff (similar to the removed loop).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools