From 43b0f2cc95f90bba5fec88234b2c9cb5cf3b1cfa Mon Sep 17 00:00:00 2001 From: Emily Date: Mon, 15 Dec 2025 16:58:24 +0000 Subject: [PATCH] ci/github-script/bot: skip mergeability checks temporarily MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is an experiment and can be reverted a few days from now; if the results are positive on GitHub’s end, then we may want to make the merge conflict checks run less frequently than the rest of the labelling tasks. (cherry picked from commit 18b30c8ce1eed9ff2e86128036b674e9e3796aaa) --- ci/github-script/bot.js | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/ci/github-script/bot.js b/ci/github-script/bot.js index f178b60287835..ffa71892c1e89 100644 --- a/ci/github-script/bot.js +++ b/ci/github-script/bot.js @@ -145,10 +145,22 @@ module.exports = async ({ github, context, core, dry }) => { // This API request is important for the merge-conflict label, because it triggers the // creation of a new test merge commit. This is needed to actually determine the state of a PR. + // + // NOTE (2025-12-15): Temporarily skipping mergeability checks here + // on GitHub’s request to measure the impact of the resulting ref + // writes on their internal metrics; merge conflicts resulting from + // changes to target branches will not have labels applied for the + // duration. The label should still be updated on pushes. + // + // TODO: Restore mergeability checks in some form after a few days + // or when we hear back from GitHub. const pull_request = ( await github.rest.pulls.get({ ...context.repo, pull_number, + // Undocumented parameter (as of 2025-12-15), added by GitHub + // for us; stability unclear. + skip_mergeability_checks: true, }) ).data