Repository navigation
tools: skip dependency update if PR has non-bot commits - #66503
Merged
nodejs-github-bot merged 1 commit intoOct 18, 2026
Merged
nodejs-github-bot merged 1 commit into
nodejs-github-bot merged 1 commit into
Conversation
Collaborator
|
Review requested:
|
nodejs-github-bot
added
the
meta
jasnell
approved these changes
Oct 4, 2026
panva
approved these changes
Oct 4, 2026
aduh95
reviewed
Oct 5, 2026
aduh95
reviewed
Oct 5, 2026
aduh95
reviewed
Oct 5, 2026
When the tools-deps-update workflow finds a new version of a dependency, peter-evans/create-pull-request force-pushes the Action's branch, discarding any commits a collaborator pushed to the existing PR to fix the update. On scheduled runs and on manual runs for all dependencies, check whether the open PR for the Action's branch contains commits not authored by the bot before running the updater, and if so skip the update for that dependency instead of overwriting them. A manual run for a single dependency still updates the PR, as it is assumed to be an intentional override. Signed-off-by: Marco Ippolito <marcoippolito54@gmail.com> Assisted-by: claude:opus-5.5
marco-ippolito
force-pushed
the
tools-skip-update-on-human-commits
branch
from
October 18, 2026 09:22
2e5f6b4 to
f37531c
Compare
aduh95
approved these changes
Oct 18, 2026
aduh95
left a comment
aduh95
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Additional suggestion: have the bot comment on the existing PR with a link to the workflow when it skips the update, with the suggestion to run the workflow manually if the existing commits should be overridden
marco-ippolito
added
the
commit-queue
Collaborator
|
Landed in 947b9a3 |
nodejs-github-bot
removed
the
commit-queue
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
5 participants
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.
When a new version of a dependency comes out, it runs
create pull requeston the existingactions/tools-update-<id>branch. That force-pushes the branch and throws away any commits a collaborator pushed to fix the update, as happened in #66397 and #66146.This adds a first step that checks the open PR for that branch. If any commit isn't authored by
github-bot@iojs.org, the rest of the job is skipped for that dependency and a notice links to the PR. If there's no open PR, or it only has bot commits, the update runs as before.