alamb opened a new pull request, #11795: URL: https://github.com/apache/arrow-rs/pull/11795
# Which issue does this PR close? N/A # Rationale for this change CI on `main` sometimes fails even though nothing is wrong with the code. For example, in https://github.com/apache/arrow-rs/actions/runs/39576843746: - [docs / deploy](https://github.com/apache/arrow-rs/actions/runs/39576843746/job/119336871264) failed - which made [Required Checks](https://github.com/apache/arrow-rs/actions/runs/39576843746/job/119462180830) fail The deploy job fails with ``` ! [remote rejected] asf-site -> asf-site (cannot lock ref 'refs/heads/asf-site': is at 8a6c3e45... but expected 4b2fb0d7...) ``` This happens when two commits are pushed to `main` close together. The CI concurrency group is keyed on the commit SHA, so both runs execute in parallel, and both `deploy` jobs force push the `asf-site` branch at the same time. Whichever push lands second is rejected. In the example above, the sibling run for the previous commit (https://github.com/apache/arrow-rs/actions/runs/39576767981) started its deploy in the same second and succeeded. # What changes are included in this PR? Add a job level `concurrency` group to the `deploy` job in `docs.yml` so docs deploys run one at a time. `cancel-in-progress: false` plus `queue: max` means every push to `main` still publishes its docs, in order, instead of racing or being cancelled. `queue: max` was added by GitHub in May 2026: https://github.blog/changelog/2026-05-07-github-actions-concurrency-groups-now-allow-larger-queues # Are these changes tested? `python3 .github/ci/scripts/check-ci-config.py` passes. The deploy job only runs on pushes to `main`, so the real test is watching `main` after merge. # Are there any user-facing changes? No. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
