docs: merge-queue enablement + GitHub Actions dependency facts#114
Merged
Conversation
The skill covered merge-queue behavior and troubleshooting but not how to turn one on. Adds an 'Enabling a merge queue' section: the ruleset REST payload (classic branch-protection cannot toggle it; the merge_queue rule is repo-level only), the merge_queue parameters with their gotchas (SQUASH/MERGE signed vs REBASE unsigned, ALLGREEN vs HEADGREEN, the check-response timeout as an eject trigger, min_entries_to_merge_wait being inert when the minimum is 1), integration_id pinning of required checks, single-surface enablement with strict dropped as redundant, and evaluate-mode dry-run plus one-call rollback. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
…arning verification Two GitHub Actions facts: - Dependabot rewrites the trailing '# vX.Y.Z' comment together with the SHA, so annotating bare pins once (with API-verified tags) puts them in the format it maintains; without the github-actions ecosystem, pins only drift by hand. - A runtime-deprecation warning (e.g. Node 20) is only cleared by a bump if the newer release changed the runtime — check the target version's action.yml runs.using before claiming a bump fixes it; an action already at latest can still warn. Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
documentation
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
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.
From a retro on a render-guides merge-queue rollout (TYPO3-Documentation/render-guides#1326 + a Dependabot-actions split). The skill covered merge-queue behavior and troubleshooting thoroughly but nothing on enablement, and two GitHub Actions dependency facts came up that weren't documented.
references/merge-strategy.md— "Enabling a merge queue"merge_queuerule is repo-level only (org rulesets reject it).POST /rulesetspayload with themerge_queueparameters and their gotchas: SQUASH/MERGE signed vs REBASE unsigned,ALLGREENvsHEADGREEN,check_response_timeout_minutesas an eject trigger,min_entries_to_merge_wait_minutesinert when the minimum is 1,integration_id: 15368pinning required checks to the Actions app, single-surface enablement with the classicstrictflag dropped as redundant,evaluatedry-run + one-call rollback.references/dependency-management.md— SHA-pin comments & deprecation warnings# vX.Y.Zcomment together with the SHA — annotating bare pins once (API-verified tags) puts them in the format it maintains.action.ymlruns.usingbefore claiming a bump fixes it.markdownlint-cli2: 0 errors. No version bump (matches the recent docs PRs #111–#113).