You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
pr-queue lens rules: follow-ups from #283's lenses #303
Follow-ups from the lenses on #283 (pr-queue lens rules): bypass #283 (round 1, SAFE) and state round 2 #283 (comment) (SAFE). None blocks. All in fork-ci/actions/pr-queue/lens.py and its docs.
minor, nested markup cleaned twice. The queue cleans its quote once; the reader cleans it again. With nested tags or links (lens<<a>b>= …, lens[[](z)](w)= …) the reader's second pass makes lens=, so the queue's own turn-off comment is flagged. Main already did this for lens: (not a regression; fails closed; needs a counted author writing nested markup on purpose). Fix: after cleaning, replace <, >, [, ] with spaces, or clean until nothing changes.
minor, a line with a lens field form and a sha blocks; not a lens: cannot clear it. Plain English like "the security lens — fixed in abc1234f" blocks. Add to the lens-format doc and the fix-round template: put shas on their own line or quote them with >.
minor, carried from round 1. A fence line with a language name closes an open fence (lens.py:231); a second header written Lens — below a valid one is not counted (:251). Plus the two mutation gaps the round-1 bypass lens named.
State question for each fix: the rules are pure functions of the comments, so the same comments must give the same answer; replay the recorded corpus and say which answers change.
Activity
fix(pr-queue): lens rules follow-ups from #283's lenses (#303) (#591)
fix(pr-queue): lens rules follow-ups from #283's lenses (#303) (#591)