Skip to content

Conversation

@pquentin
Copy link
Member

We should only save on pushes to main and other branches, and restore only in pull requests. Currently, pull request runs pollute the cache.

We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.
@github-actions
Copy link
Contributor

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

You can validate these APIs yourself by using the make validate target.

@pquentin pquentin merged commit bbf7ad2 into main Oct 15, 2025
14 checks passed
@pquentin pquentin deleted the validation-cache-only-save-on-push branch October 15, 2025 09:02
github-actions bot pushed a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)
@github-actions
Copy link
Contributor

The backport to 9.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.1 9.1
# Navigate to the new working tree
cd .worktrees/backport-9.1
# Create a new branch
git switch --create backport-5489-to-9.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 bbf7ad2c06b6fcfd5aa1b51c6951d4716d392044
# Push it to GitHub
git push --set-upstream origin backport-5489-to-9.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.1

Then, create a pull request where the base branch is 9.1 and the compare/head branch is backport-5489-to-9.1.

github-actions bot pushed a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)
pquentin added a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)
@pquentin
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
9.1

Questions ?

Please refer to the Backport tool documentation

pquentin added a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)
pquentin added a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
pquentin added a commit that referenced this pull request Oct 15, 2025
We should only save on pushes to main and other branches, and restore only in
pull requests. Currently, pull request runs pollute the cache.

(cherry picked from commit bbf7ad2)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants