Support adding the `commit-queue` label before the wait time is over

[targos]

Maybe this needs to be implemented mostly in node-core-utils, but I'd like to open the discussion here first for visibility.

I think we should be able to add the commit-queue label to a PR when the only missing requirement for it to land is the wait time. It is always annoying to have to calculate the remaining time and then remember to come back to a pull request just to add this label.

Is it desirable and implementable?

@nodejs/actions

[aduh95]

Having the commit-queue Add this label to land a pull request using GitHub Actions. label added before a PR is actually ready to land forces the scheduled GHA to do a lot more of work (it now has to fetch the full commit history, install ncu, etc.) which can delay the launch of regular CI runs on other PRs if we've reached the max number of active runners. For example, it's already possible to add the label while the CI is still running, but I've recommended against doing that because of that (and also we never know if the CI will be successful or not).

If there was a way of doing that without the need of fetching the entire commit history, that could be interesting. Otherwise, there's always the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label.

[MoLow]

why do we need the full commit history?

[aduh95]

node/.github/workflows/commit-queue.yml

Lines 53 to 55 in 7ed44db

	# Needs the whole git history for ncu to work
	# See https://github.com/nodejs/node-core-utils/pull/486
	fetch-depth: 0

[MoLow]

@aduh95 my PR filters pr prior to this checkout step

[Jimimaku]

Maybe this needs to be implemented mostly in node-core-utils, but I'd like to open the discussion here first for visibility.

I think we should be able to add the commit-queue label to a PR when the only missing requirement for it to land is the wait time. It is always annoying to have to calculate the remaining time and then remember to come back to a pull request just to add this label.

Is it desirable and implementable?

@nodejs/actions