Skip to content

Conversation

@llvmbot
Copy link
Member

@llvmbot llvmbot commented Oct 22, 2025

Backport 59d4d5c

Requested by: @tstellar

…ing workflow (llvm#162765)

This should fix the part of the workflow that creates a PR with the new
documentation.

(cherry picked from commit 59d4d5c)
@llvmbot
Copy link
Member Author

llvmbot commented Oct 22, 2025

@boomanaiden154 What do you think about merging this PR to the release branch?

@llvmbot
Copy link
Member Author

llvmbot commented Oct 22, 2025

@llvm/pr-subscribers-github-workflow

Author: None (llvmbot)

Changes

Backport 59d4d5c

Requested by: @tstellar


Full diff: https://github.com/llvm/llvm-project/pull/164538.diff

2 Files Affected:

  • (modified) .github/workflows/release-documentation.yml (+4)
  • (modified) .github/workflows/release-tasks.yml (+3)
diff --git a/.github/workflows/release-documentation.yml b/.github/workflows/release-documentation.yml
index 5a0aa063d32ac..e07da3d9f3009 100644
--- a/.github/workflows/release-documentation.yml
+++ b/.github/workflows/release-documentation.yml
@@ -25,6 +25,10 @@ on:
         description: 'Upload documentation'
         required: false
         type: boolean
+    secrets:
+      WWW_RELEASES_TOKEN:
+        description: "Secret used to create a PR with the documentation changes."
+        required: false
 
 jobs:
   release-documentation:
diff --git a/.github/workflows/release-tasks.yml b/.github/workflows/release-tasks.yml
index c9ae7e1ce97c3..894661a5112d5 100644
--- a/.github/workflows/release-tasks.yml
+++ b/.github/workflows/release-tasks.yml
@@ -54,6 +54,9 @@ jobs:
     with:
       release-version: ${{ needs.validate-tag.outputs.release-version }}
       upload: true
+    # Called workflows don't have access to secrets by default, so we need to explicitly pass secrets that we use.
+    secrets:
+      WWW_RELEASES_TOKEN: ${{ secrets.WWW_RELEASES_TOKEN }}
 
   release-doxygen:
     name: Build and Upload Release Doxygen

@c-rhodes c-rhodes moved this from Needs Triage to Needs Merge in LLVM Release Status Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Needs Merge

Development

Successfully merging this pull request may close these issues.

3 participants