Separate code_checks and doc_checks

Author: vdusek

.github/workflows/build_and_deploy_docs.yaml

@@ -11,7 +11,12 @@ env:
   PYTHON_VERSION: 3.14
 
 jobs:
+  doc_checks:
+    name: Doc checks
+    uses: ./.github/workflows/doc_checks.yaml
+
   build_and_deploy_docs:
+    needs: [doc_checks]
     environment:
       name: github-pages
     permissions:

.github/workflows/run_code_checks.yaml .github/workflows/code_checks.yaml.github/workflows/run_code_checks.yaml renamed to .github/workflows/code_checks.yaml

@@ -50,10 +50,6 @@ jobs:
     name: Async dostrings check
     uses: ./.github/workflows/_async_docstrings_check.yaml
 
-  docs_check:
-    name: Docs check
-    uses: apify/workflows/.github/workflows/python_docs_check.yaml@main
-
   integration_tests:
     name: Integration tests
     needs: [lint_check, type_check, unit_tests]

.github/workflows/doc_checks.yaml

@@ -0,0 +1,20 @@
+name: Run doc checks
+
+on:
+  # Trigger code checks on opening a new pull request.
+  # Secrets are only made available to the integration tests job, with a manual approval
+  # step required for PRs from forks. This prevents their potential exposure.
+  pull_request:
+
+  # Trigger for pushing to the master branch is handled by the build-and-deploy-docs workflow.
+
+  # It should also be possible to trigger checks manually
+  workflow_dispatch:
+
+  # Allow this workflow to be invoked as a reusable workflow from other workflows
+  workflow_call:
+
+jobs:
+  doc_checks:
+    name: Run doc checks
+    uses: apify/workflows/.github/workflows/python_docs_check.yaml@main

.github/workflows/pre_release.yaml

@@ -34,7 +34,7 @@ jobs:
 
   run_code_checks:
     name: Run code checks
-    uses: ./.github/workflows/run_code_checks.yaml
+    uses: ./.github/workflows/code_checks.yaml
 
   update_changelog:
     name: Update changelog