Add check for `Reviewed-By:` line to merge.sh by sxa · Pull Request #64363 · nodejs/node

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa · 2026-07-08T15:20:50Z

Identified after I used merge.sh myself and it didn't pick up the absence of the Reviewed-By: lines
This will stop it happening again.

Signed-off-by: Stewart X Addison <sxa@ibm.com>

nodejs-github-bot · 2026-07-08T15:20:55Z

Review requested:

@nodejs/actions

aduh95 · 2026-07-08T15:50:04Z

+git log -1 HEAD --pretty='format:%B' | git interpret-trailers --parse --no-divider | \
+ grep -q "^Reviewed-By: " || {
+ echo "No Reviewed-By: lines in the commit message"
+ exit 1
+ }


Really it should run core-validate-commit, there are many more things that could go wrong – maybe we can also document somewhere that humans are never ever supposed to write a PR-URL trailer manually

I'm not sufficiently familiar with core-validate-commit to make that change but if it can be called from here then that would probably make more sense.

I also considered adding an extra message to the error here (and on the PR-URL check) to say "Have you run 'git node land' first?" which would discourage an manual adding of the lines.

Added additional message. Let me know if you're happy with the wording.

I'm not sufficiently familiar with core-validate-commit to make that change
With all due respect, if you can't figure that out, you probably shouldn't be using that script at all. Folks should be landing commits using the CQ, this script was added for power users to use when the edge cases that CQ won't handle – by "power user", what I mean is someone who knows what they're doing, and are able to fix their mistakes.
I'm not sure the use case of "the user amended the commit message" is covered by the added check, the mere presence of a Reviewed-by trailer says nothing about the validity of the commit message – but also, given that tool is meant for power users, do we actually want to try to outsmart the user? FWIW on GH we only enfore the PR-URL trailer as well, so if you had git pushed (or used the GH web UI) instead of using the script, you would have come to the same result. If we want to enforce Reviewed-by, that should happen at the GH level, not in this script IMO (and I'm not sure we need to enforce it, because it might have been the first time it has happened since we added the GH rule enforcing that PR-URL trailer is present)

With all due respect, if you can't figure that out, you probably shouldn't be using that script at all.
My statement was more about the fact I hadn't looked at it before rather than not being able to figure it out.
While it would certainly be possible to include that I'm not sure we'd want to add a dependency on that into the script though since I don't think it currently has any other dependency on node itself currently.
But if you don't think this additional check and notice is appropriate for any use case I'll close the PR.

since I don't think it currently has any other dependency on node itself currently.
It doesn't have a dependency on node AFAICT, the dependencies are listed in
node/tools/actions/merge.sh
Line 3 in 116302d
# Requires [gh](https://cli.github.com/), [jq](https://jqlang.github.io), git, and grep. Also awk if you pass a URL.
I'm not sure we'd want to add a dependency on that into the script
Definitely agree on that, adding deps should not be done lightly.
But if you don't think this additional check and notice is appropriate for any use case
My point is that if we're adding a check, it shouldn't go on merge.sh – it should be set as a rule on GH so it covers git push and folks using the web UI.
I'll close the PR
Well I would still land the wording change reminding the user if they ran git node land

Signed-off-by: Stewart X Addison <sxa@ibm.com>

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

tools: add check for Reviewed-by: to merge.sh
ccc1806
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa requested a review from aduh95 July 8, 2026 15:20

sxa self-assigned this Jul 8, 2026

nodejs-github-bot added the tools Issues and PRs related to the tools directory. label Jul 8, 2026

aduh95 reviewed Jul 8, 2026
View reviewed changes

Adjust messages to suggest git node land
7f944e6
Signed-off-by: Stewart X Addison <sxa@ibm.com>

sxa closed this Jul 9, 2026

sxa mentioned this pull request Jul 14, 2026
tools: reference 'git node land' in PR-URL: error message in merge.sh #64495
Merged

Uh oh!

Uh oh!

Conversation

sxa commented Jul 8, 2026

Uh oh!

nodejs-github-bot commented Jul 8, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

sxa commented Jul 8, 2026

Uh oh!

nodejs-github-bot commented Jul 8, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

sxa commented Jul 8, 2026

Uh oh!

nodejs-github-bot commented Jul 8, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers