-
Notifications
You must be signed in to change notification settings - Fork 115
Stop saving GitHub cache on pull requests #5489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
We should only save on pushes to main and other branches, and restore only in pull requests. Currently, pull request runs pollute the cache.
|
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 |
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)
|
The backport to 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.1Then, create a pull request where the |
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)
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)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
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>
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>
We should only save on pushes to main and other branches, and restore only in pull requests. Currently, pull request runs pollute the cache.