[DOCS] Skip docs-build-pr CI for changelogs and release bundles#276025
Closed
lcawl wants to merge 1 commit into
Closed
[DOCS] Skip docs-build-pr CI for changelogs and release bundles#276025lcawl wants to merge 1 commit into
lcawl wants to merge 1 commit into
Conversation
lcawl
marked this pull request as ready for review
July 2, 2026 16:15
|
Pinging @elastic/experience-docs (Team:Docs) |
Contributor
💚 Build Succeeded
|
cotti
approved these changes
Jul 2, 2026
jbudz
approved these changes
Jul 2, 2026
Contributor
Author
|
The better long-term solution is in elastic/docs#3343 so I'll close this one |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the
docs-buildworkflow such that when a PR only changesdocs/changelog/ordocs/releasesfiles (such as in #275684), the CI does not run.The workflow is skipped only when all changed files match that ignored path; if the PR also changes anything outside those folders, it still runs.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenarios- [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list- [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.- [ ] Flaky Test Runner was used on any tests changed- [ ] The PR description includes the appropriate Release Notes section, and the correctrelease_note:*label is applied per the guidelines- [ ] Review the backport guidelines and apply applicablebackport:*labels.Identify risks
N/A