Noticed repeatedly (during handling #144 and 'merge everything'): even after gh pr update-branch and all checks reporting SUCCESS, merge is blocked with '11 of 11 required status checks are expected' or BEHIND/UNKNOWN.
Release-please PRs end up with auto-merge set but may not land promptly due to ruleset strictness or check staleness.
This was noticed (policy errors in tools) but we didn't investigate/fix the ruleset config or add special handling for release PRs (beyond existing label skips in auto-approve).
Noticed repeatedly (during handling #144 and 'merge everything'): even after gh pr update-branch and all checks reporting SUCCESS, merge is blocked with '11 of 11 required status checks are expected' or BEHIND/UNKNOWN.
Release-please PRs end up with auto-merge set but may not land promptly due to ruleset strictness or check staleness.
This was noticed (policy errors in tools) but we didn't investigate/fix the ruleset config or add special handling for release PRs (beyond existing label skips in auto-approve).