Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: e36d6bec86101d75d794fbd0b931f2e42c91af6b https://github.com/xwiki/xwiki-dev-llm/commit/e36d6bec86101d75d794fbd0b931f2... Author: Vincent Massol <[email protected]> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stay quiet about a CI incident an open PR already answers * Add `fix-in-flight` to `fixState`: an open PR whose title or body names the failing test class, or the JIRA key the incident is tracked as, buys the same silence a landed-but-unbuilt commit does — no deep slot, no commit comment, one line in the paste. Root-causing a test somebody is visibly working on is arguing with the room. * Run it only where the branch itself holds nothing: a landed commit will be judged by the next build, a PR is somebody's intent, and the stronger evidence is what the reader needs. Inherits S1's coverage rule whole — a PR answering one failing class of two leaves the incident live, with its blame and its comment. * Read the open PRs once per repo per run, never per incident: the plain `pulls` list newest-updated first, stopping at the first PR outside a 14-day window, three pages at most. That is 1-2 requests for xwiki-platform's ~230 open PRs, on the core quota rather than the search API's own budget. * Require the PR's base branch to be the incident's branch. A master PR cannot fix `stable-17.10.x`, and silencing that branch on it would hide a break nobody is working on. * Let a JIRA key answer for the whole incident only when the incident is a single test class — the key is the flicker issue of its first test and says nothing about classes that merely broke in the same build. * Give `fixState` a `where` clause and a per-kind headline, so the four places that render it stop spelling out one kind's story and the next value is a row in a table rather than a branch in each of them. * Word it *may be in flight*, never *fixed*: the PR may be a rewrite that touches the test, and it may never merge. What settles it is the merge, not this run. Verified against xwiki-platform/master: the live sweep is unchanged (the one answered incident is still `fix-unbuilt`, and no open PR names the other three), and a probe with the forward pass short-circuited matches `#6456` and correctly reports it as partial. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Commit: 802a3df5870cf42e6418759e0c3313dfbe34be06 https://github.com/xwiki/xwiki-dev-llm/commit/802a3df5870cf42e6418759e0c3313... Author: Vincent Massol <[email protected]> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- Merge pull request #152 from xwiki/ci-check-in-flight-fix [Misc] Stay quiet about a CI incident an open PR already answers Compare: https://github.com/xwiki/xwiki-dev-llm/compare/3014ce3944f5...802a3df5870c To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications