-
Notifications
You must be signed in to change notification settings - Fork 106
Output validation comments even without changes #4781
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
Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken.
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 |
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-8.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-4781-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 bbd5dcf5faa025686e452ce20e87a4e9b5bd6a68
# Push it to GitHub
git push --set-upstream origin backport-4781-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19 Then, create a pull request where the |
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-8.18 8.18
# Navigate to the new working tree
cd .worktrees/backport-8.18
# Create a new branch
git switch --create backport-4781-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 bbd5dcf5faa025686e452ce20e87a4e9b5bd6a68
# Push it to GitHub
git push --set-upstream origin backport-4781-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18 Then, create a pull request where the |
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.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-4781-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 bbd5dcf5faa025686e452ce20e87a4e9b5bd6a68
# Push it to GitHub
git push --set-upstream origin backport-4781-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0 Then, create a pull request where the |
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf)
* Output validation comments even without changes Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken. * Adjust output * Try fixing branch name * Stop trying to display the target branch (cherry picked from commit bbd5dcf) Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>
Otherwise, a PR that breaks validation but then restores it will keep a comment saying that validation is broken.