Update PR comments in place #4620
Merged
Conversation
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
Currently, we post a new comment for each change, which is just spam for PRs with many iterations.
flobernd
approved these changes
Jun 19, 2025
.github/workflows/validate-pr.yml
Outdated
| run: node .github/validate-pr --token ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - name: Find existing comment | ||
| uses: peter-evans/find-comment@v3 |
There was a problem hiding this comment.
Let's pin external dependencies by commit hash.
.github/workflows/validate-pr.yml
Outdated
|
|
||
| - name: Create or update comment | ||
| if: steps.validation.outputs.has_results == 'true' | ||
| uses: peter-evans/create-or-update-comment@v4 |
pquentin
added
backport 8.19
backport 8.18
backport 9.0
and removed
skip-backport
|
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-4620-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 914b5d82aed66edbb9d2adf0671fd3f233836957
# Push it to GitHub
git push --set-upstream origin backport-4620-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0Then, 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-4620-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 914b5d82aed66edbb9d2adf0671fd3f233836957
# Push it to GitHub
git push --set-upstream origin backport-4620-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18Then, 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.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-4620-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 914b5d82aed66edbb9d2adf0671fd3f233836957
# Push it to GitHub
git push --set-upstream origin backport-4620-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19Then, create a pull request where the |
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
* Update PR comments in place Currently, we post a new comment for each change, which is just spam for PRs with many iterations. * Pin actions by hash (cherry picked from commit 914b5d8)
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
* Update PR comments in place Currently, we post a new comment for each change, which is just spam for PRs with many iterations. * Pin actions by hash (cherry picked from commit 914b5d8)
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
* Update PR comments in place Currently, we post a new comment for each change, which is just spam for PRs with many iterations. * Pin actions by hash (cherry picked from commit 914b5d8)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
pquentin
added a commit
that referenced
this pull request
Jun 24, 2025
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.
Currently, we post a new comment for each change, which is just spam for PRs with many iterations.
Tested in pquentin#2.