Skip to content

ci: enable use-release-branches for docs workflows#50098

Merged
bmorelli25 merged 2 commits intoelastic:mainfrom
Mpdreamz:chore/docs-use-release-branches
Apr 14, 2026
Merged

ci: enable use-release-branches for docs workflows#50098
bmorelli25 merged 2 commits intoelastic:mainfrom
Mpdreamz:chore/docs-use-release-branches

Conversation

@Mpdreamz
Copy link
Copy Markdown
Member

@Mpdreamz Mpdreamz commented Apr 13, 2026

Summary

Enables the use-release-branches input on the reusable docs-build and docs-deploy workflows from elastic/docs-actions (@v1).

That lets release-line branches (e.g. 9.4) refresh the shared link index and run a docs build when needed, even if a push does not touch docs/ (common after branch cut).

Related

  • The use-release-branches input is available on the reusable workflows behind @v1 as of docs-actions v1.7.9.

Pairs with elastic/docs-actions reusable workflows: release-line pushes can
refresh the shared link index even when commits do not touch docs/.

Backport the same two workflow edits to branches 9.3 and 9.4 after merge.

Made-with: Cursor
@Mpdreamz Mpdreamz requested a review from a team as a code owner April 13, 2026 17:25
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 13, 2026

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @Mpdreamz? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 13, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 56d851dc-938a-4793-87a8-2cb1ef7e54be

📥 Commits

Reviewing files that changed from the base of the PR and between d1a9d04 and 0dc9364.

📒 Files selected for processing (2)
  • .github/workflows/docs-build.yml
  • .github/workflows/docs-deploy.yml
✅ Files skipped from review due to trivial changes (1)
  • .github/workflows/docs-build.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/docs-deploy.yml

📝 Walkthrough

Walkthrough

Two documentation workflow files were updated to include a new input configuration. In .github/workflows/docs-build.yml and .github/workflows/docs-deploy.yml, the use-release-branches: true input was added to their reusable workflow invocations delegating to elastic/docs-actions (v1). No other workflow triggers, permissions, jobs, or control flow were changed. Total additions: 2 lines across both files.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • 🛠️ Update Documentation: Commit on current branch
  • 🛠️ Update Documentation: Create PR

Comment @coderabbitai help to get the list of available commands and usage tips.

@Mpdreamz Mpdreamz added Team:Docs Label for the Observability docs team backport-9.3 Automated backport to the 9.3 branch backport-9.4 labels Apr 13, 2026
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 13, 2026
@Mpdreamz Mpdreamz added backport-9.3 Automated backport to the 9.3 branch and removed backport-9.3 Automated backport to the 9.3 branch labels Apr 13, 2026
@bmorelli25 bmorelli25 merged commit 3fb6501 into elastic:main Apr 14, 2026
22 of 28 checks passed
mergify bot pushed a commit that referenced this pull request Apr 14, 2026
* ci: enable use-release-branches for docs-build and docs-deploy

Pairs with elastic/docs-actions reusable workflows: release-line pushes can
refresh the shared link index even when commits do not touch docs/.

Backport the same two workflow edits to branches 9.3 and 9.4 after merge.

Made-with: Cursor

* chore: drop backport comment from docs workflow YAML

Made-with: Cursor
(cherry picked from commit 3fb6501)

# Conflicts:
#	.github/workflows/docs-build.yml
#	.github/workflows/docs-deploy.yml
mergify bot pushed a commit that referenced this pull request Apr 14, 2026
* ci: enable use-release-branches for docs-build and docs-deploy

Pairs with elastic/docs-actions reusable workflows: release-line pushes can
refresh the shared link index even when commits do not touch docs/.

Backport the same two workflow edits to branches 9.3 and 9.4 after merge.

Made-with: Cursor

* chore: drop backport comment from docs workflow YAML

Made-with: Cursor
(cherry picked from commit 3fb6501)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-9.3 Automated backport to the 9.3 branch backport-9.4 skip-changelog Team:Docs Label for the Observability docs team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants