tools: commit-queue wait 2 days automatically#45407
tools: commit-queue wait 2 days automatically#45407nodejs-github-bot merged 1 commit intonodejs:mainfrom
Conversation
|
Review requested:
|
|
CC @targos |
|
This would force us to land
fast-track
|
You can use https://github.com/nodejs/node-auto-test for this kind of things. |
I guess we can merge the result of two queries |
|
@aduh95 added support for
fast-track
|
|
@panva @aduh95 tested: the commit queue resulted in attempting to commit PRs 31 (commit-queue & < 2 days) and 50 (commit-queue & fast track): |
|
amazing @panva :) too bad I cannot use this on this PR yet :/ |
|
If we could query for number of approvals we could also add minimum 2 to the 2 day query and add a third query for minimum 1 and 7 days ;) |
ncu already does that |
by then the label is removed and ncu will fail the commit queue. |
|
Yeah 😐 |
|
But it's mostly crypto and cpp PRs that don't manage to get at least two approvals in 2 days. This is still a great feature. Add CQ label as soon as you have two or enough fast track thumbs. Then stop worrying about the PR. |
| numbers=$(echo $prs' '$fast_track_prs | jq -r -s 'unique | join(" ")') | ||
| echo "numbers=$numbers" >> $GITHUB_OUTPUT |
There was a problem hiding this comment.
nit
| numbers=$(echo $prs' '$fast_track_prs | jq -r -s 'unique | join(" ")') | |
| echo "numbers=$numbers" >> $GITHUB_OUTPUT | |
| echo "numbers=$(echo $prs' '$fast_track_prs | jq -r -s 'unique | join(" ")')" >> $GITHUB_OUTPUT |
There was a problem hiding this comment.
I prefer to minimize changes after I completed testing
|
Note: the commit message should start with a verb after the subsystem (and the subsystem should probably be |
7160ddc to
bf4f077
Compare
|
Landed in 119559a |

Fixes: #45405
not sure how we can test this