tools: improve commit queue failure comment

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275

[panva]

Commit Queue failure comments currently hide the actionable reason and recovery steps inside the collapsed git node land output. This made e.g. a missing multiple-commit landing policy look like a generic queue failure.

Surface a concise reason before the full output. Give the missing policy case specific commit-queue-squash and commit-queue-rebase guidance. For other failures, show up to ten warning and error lines, falling back to the end of the output when none are tagged. These diagnostics preserve line breaks while allowing long lines to wrap.

Also explain how to retry, retain the full escaped output in a disclosure, and use a descriptive workflow link. Push and squash-merge failures now supply explicit reasons.

For a missing multiple-commit policy, the comment previously rendered as:

▸ Commit Queue failed

It now renders as:

Commit Queue failed

This pull request has multiple commits, but no landing policy was selected.

Add commit-queue-squash to land it as one commit, or commit-queue-rebase to land the commits separately.

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

Other failures now surface their relevant output, for example:

Commit Queue failed

✘ No Jenkins CI runs detected

The pull request was removed from the Commit Queue and labeled commit-queue-failed. After resolving the failure, remove that label and add commit-queue to retry.

▸ Full Commit Queue output

View workflow run

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

LGTM with a few nits

[nodejs-github-bot]

Landed in f411275