Allow scheduled deploy after partial failures (#21)

Agent-Logs-Url: https://github.com/m-aciek/python-docs-offline/sessions/ebcace79-8f8a-48d2-b4db-3a97205a14b1

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: m-aciek <9288014+m-aciek@users.noreply.github.com>

Author: Copilot

.github/workflows/schedule.yaml

@@ -92,7 +92,7 @@ jobs:
     # Artifacts from every concurrent build job are merged here and published
     # once via actions/deploy-pages, eliminating concurrent gh-pages push conflicts.
     needs: build
-    if: ${{ !cancelled() && needs.build.result != 'failure' && github.event_name != 'push' }}
+    if: ${{ always() && !cancelled() && needs.build.result != 'skipped' && github.event_name != 'push' }}
     runs-on: ubuntu-latest
     environment:
       name: github-pages

README.md

@@ -26,8 +26,8 @@ cycle API and the docsbuild-scripts configuration to determine which
 the [build.yaml](.github/workflows/build.yaml) reusable workflow, which checks
 out the CPython source, builds the documentation with Sphinx, and uploads the
 resulting archives as artifacts. After all builds complete, a single deploy job
-merges the artifacts into the `gh-pages` branch and publishes them to GitHub
-Pages.
+merges the successfully generated artifacts into the `gh-pages` branch and
+publishes them to GitHub Pages, even if some builds failed.
 
 ## Rejected idea