Skip to content

feat(crewmate-chat): fold a run of steps into one live line with a quiet finished summary - #18221

Closed
iamwhatever wants to merge 1 commit into
mainfrom
feat/crewmate-work-line
Closed

iamwhatever wants to merge 1 commit into
mainfrom
feat/crewmate-work-line

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: While a crewmate works, its chat shows one line that says it is working and what step it is on, instead of a growing list of tool rows; when the turn ends the steps fold away, as they already do since #17794.

In a crewmate's chat on the Crew page, a running turn draws every tool call and thinking burst as its own row (Verify heads and build approve/RC bodies, Post 5 approvals…, Merge clean PRs…, each with a status dot), plus the ghost working animation below them. A 1:1 chat with a crewmate reads like a log, not a conversation, and shows two "working" indicators at once.

Why it matters

The Crew page chat is meant to read like messaging a teammate. A wall of step rows pushes the crewmate's actual words off screen and makes every patrol look noisy; the reader only needs to know that it is working and on what, with the detail one click away.

Not a goal

  • Ordinary (non-crew) chats: their tool rows, step groups and footer are unchanged.
  • The crewmate's Work log panel and what it records.
  • Finished turns: their steps still fold away when the turn ends (feat(crew): show live tool progress and outline the crewmate bubble #17794); this PR draws nothing new for them.
  • Restyling the tool line or thinking block themselves; the opened list reuses them as they are.

What changed (motivation → approach → change)

A crewmate's live tool rows were drawn one per row because #17794 only filtered which rows the chat keeps; nothing grouped them. The grouping now happens in the same place: filterCrewmateChat folds each contiguous run of the running turn's progress rows into one synthetic crewmate_steps row carrying the folded rows, their tool-call count and whether it is the step the crewmate is on now (the run with nothing drawn after it). A run that the crewmate has spoken after stays in place as its own quiet line, so mid-turn speech stays where it was said; such an earlier run with no tool call (thinking only) has no step to count and is dropped. When the turn has no run at its tail (just opened, or just spoke) an empty live row stands in, so the turn shows one working line from start to end. The turn's trailing streaming row (text started before the tools, which the store parks below the tool rows) does not end the live run, and the footer still stands down. A run keys on its first tool call, so the live line keeps its identity and open state as steps arrive. When the turn ends, every steps line folds away, exactly as #17794 left it.

A new website/src/pages/chat/CrewmateStepsLine.tsx draws that row as one disclosure button, the shared Btn flattened to a text line (aria-expanded, aria-controls, a native button so Enter and Space work). Live: the tool line's own spinning ring (still under prefers-reduced-motion), the current step's title (the slot's live tool status, else the newest call's purpose or title, else "Thinking"; wrapping in full on narrow screens rather than cut, with a tooltip) and "N steps"; open, the heading keeps only the count, since the running row below names the step; before the first step a plain "Thinking" line with nothing to open. An earlier run of the same turn reads "Worked through N steps", the existing pages.chat.turnBlock.worked_through_step summary. Opened, it draws the folded rows, indented past the chevron, through the same renderer registry, so each is the ordinary tool line with its own live state (running, done, failed) from the slot's tool log. The crewmate renderer set in website/src/pages/chat/transcriptRenderers.tsx gains the entry; ChatPane hides its PLAIN working footer while the live line is the newest row (stopping and compacting still show), and the line carries the footer's role="status" announcement, so only one working indicator shows. The steps row is run-transparent, so bubble corners are unchanged. One new plural key pages.chat.crewmateSteps.step in every catalog under website/src/i18n/ (plus pluralKeys.json); chatRolesParity.contract.test.ts documents the new renderer id; crew-mode.md and the Crewmate chat row of docs/feature-map/README.md describe the rule.

Backwards compatibility

Compatible: only a crewmate's chat (ChatPane with crewmate) builds or draws the new row; the role never reaches the wire or any other surface.

Removes nothing: the folded rows are still drawn when the line opens, and the transcript and Work log keep every row as before.

Tests

  • crewmateBubbles.test.ts: a running turn folds into ONE live row counting only 🔧 calls (✅/🚫 siblings and thinking ride along); a thinking-only live run is still live; a settled reply after a run makes it not live; mid-turn speech keeps an earlier run as its own line; a working line shows from the turn's start and again after mid-turn speech, but not after a pending approval; a trailing streaming row parked below the tools does not end the live run; when the turn ends every steps row folds away, even when it spoke between them; an earlier turn's steps are gone; the row keys on its first step.
  • CrewmateStepsLine.test.tsx: collapsed by default; live shows the ring, current step and "3 steps"; the slot's live tool status wins; trailing thinking reads "Thinking"; the title has a tooltip; a status announcement; the open live heading keeps only the count; before the first step there is nothing to open; reduced-motion class; an earlier run reads "Worked through 3 steps" without the ring; singular; click opens/closes with aria-expanded/aria-controls; Enter opens it.
  • ChatPane.crewmate.test.tsx: a running crewmate turn draws one collapsed live line and no footer, also when a streaming row is parked below its tool rows (red against a last-row-only check); an ordinary chat with the same rows still draws its tool row and the footer, no steps line.
  • Unchanged-proof: the existing ChatPane.*, TurnBlock*, CrewmateMessage and role-parity suites pass locally, run serially (39 files).

Manual verification

Rendered the real ChatMessageList with the crewmate renderer set in Storybook (a local, uncommitted story) and captured each state below in light and dark at 320px and 1100px; checked the DOM for the line's text, the absent footer and no horizontal overflow at 320px. Local gates: tsc -p tsconfig.app.json, eslint --max-warnings 0 on the touched files, npm run i18n:check with I18N_BASE_REF=origin/main.

Screenshots / video

Before (main): the ghost footer at turn start, then one row per step plus the footer.

before start

before live

After: turn start (one working line, no footer); live collapsed; live open (each row its real state: two done, the newest spinning); mid-turn speech (earlier run stays in place, newest run live); finished (steps folded away, as on main):

live start

live collapsed

live expanded

live mid-turn

finished

Narrow (320px): the live title wraps in full instead of being cut.

live collapsed 320

Every variant (light/dark x 320px/1100px)




















Related Issues

Builds on #17794.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@iamwhatever
iamwhatever requested review from a team and KiroCrewCaptain as code owners October 8, 2026 19:40
@iamwhatever
iamwhatever requested a review from CrysisDeu October 8, 2026 19:41
@iamwhatever
iamwhatever force-pushed the feat/crewmate-work-line branch from 9adca77 to f87d886 Compare October 8, 2026 20:01
@github-actions github-actions Bot added readiness: checking Automated validation is still running merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Oct 8, 2026
@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 98bebed18aaf54bf95f0e5cbda64b4edb395b372 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that opened steps render correctly with the outer row's ctx.index/ctx.messages. The nested resolveRenderer call passes the parent context through unchanged.

[DESIGN-REVIEWED] 98bebed

Description read

[DESCRIPTION-READ] e68a962c036d140f8d16334043ac8f6ce5ac045a25e7e74abbac46220e77493e

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 98bebed18aaf54bf95f0e5cbda64b4edb395b372 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 98bebed

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 98bebed18aaf54bf95f0e5cbda64b4edb395b372: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

UX-level review of 98bebed18aaf54bf95f0e5cbda64b4edb395b372 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

The collapsed live line reads as an order: its title is the agent's imperative step text, so the reader feared clicking would start the merge.

Watch

  • The disclosure looks like an action button. CrewmateStepsLine makes the whole step title (text-text, the agent's own imperative wording) the clickable text of the toggle. The blind reader on shot-04 said: "the line reads like an order to merge, and I'd be a little afraid that clicking the words starts the merge." They still said they would click, so this is not a block. It matters because this is the PR's main control and it shows on every crewmate turn.
  • The step count reads as a running total. Each run counts only its own steps, so the user sees "3 steps", and after the crewmate speaks, "Worked through 1 step" above "2 steps". The reader said "steps seems to mean both 'all the tasks' and 'tasks still left', and the numbers don't add up." Every user hits this on any turn where the crewmate speaks mid-turn, and nothing on screen explains it.
  • The count drifts away on narrow screens. At 320px the title wraps while the shrink-0 count stays pinned to the far right (shot-08/19): "'3 steps' seems cut off from the task it belongs to." Once the line is opened, the narrow rows cut the current step off with "…" (shot-20/22). The title wraps in full only while the line is collapsed.

Suggestions

  • Put the count first and write the title as status: "3 steps · Merging clean PRs…". Keeping the step title muted and in a progress form makes it read as a label, not a command.
  • Keep the count next to the title, e.g. wrap it inline after the title instead of pinning it in its own column, so at 320px it stays beside the task.

[UX-REVIEWED] 98bebed

Description read

[DESCRIPTION-READ] fd1e1dac814b4a597522324fa6467c6ad2e7d76cdd3e6b30e980d7e9e9952028

That sha256 names everything this verdict read: the PR description, plus the 31 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 98bebed18aaf54bf95f0e5cbda64b4edb395b372 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Check before merge: a thinking-only run that comes before mid-turn speech is now dropped, so a running turn shows less thinking than it does on main.

What this change ships

Inventory (7 items) — 7 justified

Intent: let a person chatting with a crewmate see one "working on X" line instead of a growing log of step rows. This is an ADDITION.

  1. While a crewmate's turn runs, its tool and thinking rows fold into one collapsed line with a spinner, the current step's title and "N steps". — justified
  2. The pane's plain working footer hides while that line is the newest row; the line takes over its role="status" announcement. — justified
  3. A "Thinking" line shows from the start of the turn, before the first step, in place of the footer. — justified
  4. If the crewmate speaks mid-turn, the steps before it stay in place as a quiet "Worked through N steps" line. — justified
  5. An earlier run within the turn that has only thinking and no tool call is no longer drawn at all. — justified
  6. The line opens on click or Enter to show the ordinary tool and thinking rows, and stays open as new steps arrive. — justified
  7. Pending text parked below the tool rows no longer ends the live line; it is drawn after it. — justified

[FIRST-PRINCIPLES-REVIEWED] 98bebed

Description read

[DESCRIPTION-READ] 6ec38d349484ee60bffbc49e25a67f3641b6095125271aab21a1d020dce3356a

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 98bebed18aaf54bf95f0e5cbda64b4edb395b372 — this comment is updated in place on each push.

Review details

No findings block this merge.

FINDING — website/src/components/chat/crewmateBubbles.ts:191 — a live run that starts with a thinking row is keyed by that row, but const anchor = run.find(isToolCallRow) ?? run[0] moves the key to the first 🔧 row when it arrives. The renderer's dKey (crewmate-steps:${clientTs}) then changes, so a steps line the user opened while the crewmate was thinking snaps shut when its first tool call lands → Fix: key the run on keyOf(run[0]), which does not move as rows are added, instead of the first tool call.

[OPUS-REVIEWED] 98bebed

Verdict parsed from the review's SHA-scoped output markers for commit 98bebed18aaf54bf95f0e5cbda64b4edb395b372.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 98bebed18aaf54bf95f0e5cbda64b4edb395b372: <one-sentence reason>

@iamwhatever
iamwhatever force-pushed the feat/crewmate-work-line branch from f87d886 to dcfca79 Compare October 8, 2026 20:56
@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 8, 2026
@iamwhatever
iamwhatever force-pushed the feat/crewmate-work-line branch from dcfca79 to e60817e Compare October 8, 2026 21:57
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 8, 2026
@iamwhatever
iamwhatever force-pushed the feat/crewmate-work-line branch from e60817e to 82f14fe Compare October 8, 2026 23:08
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Hard swap and relocation at turn end — fixed in 82f14fe: the turn-end consolidation and its out.splice placement are removed; each run keeps its own steps line where it ran, keyed on its first tool call, so the live line is the same element once the turn ends (same place, same open state, only the words change). Test: "the line watched live is the same element once the turn ends: same key, same place". span=dbe63cfb5bbb

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Line unmounts and its count jumps — fixed in 82f14fe: no line unmounts or merges at turn end; each run line stays in place with its own count. span=7fb0136677f0

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Text changes in place with no transition — fixed in 82f14fe as far as the BLOCK goes: the element is now stable, so the change is one in-place text update ("N steps" with the ring becomes "Worked through N steps"), the same shape the ordinary ToolCallLine uses when a call finishes (spinner to done icon, no transition). span=ddd650c0c7b5

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Open line can close at turn end — fixed in 82f14fe: the key no longer changes at turn end (first tool call, not first row), so the disclosure state is carried. span=8121a9864fdc

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Reader not certain before/after were the same box — fixed in 82f14fe: they are now provably the same element (stable key test); live-mid and finished shots in the body show both lines in the same places. span=a88601530e2c

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Severity: every turn that speaks mid-way — fixed in 82f14fe: that path no longer relocates anything. span=c8e9629b3ab1

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Fix: keep one element across the change — fixed in 82f14fe: took the first option offered, a stable key, which also carries the open state. span=b7d012cb61cf

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Summary sits between two replies with no clear owner — fixed in 82f14fe: each run line now sits directly after the reply it followed and before the next one, i.e. exactly where those steps ran in time, instead of a merged summary placed between replies. span=6862fe68a00c

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Title repeats inside the opened list — rebutted: the previous UX round on dcfca79 (span c7661ffc2ebe) asked for the opposite, keep the current-step title in the open heading because the reader "can't tell which one is in progress"; the open list draws ToolCallLine rows whose running one spins, and the heading naming it is that same signal. Flipping it back would re-open the earlier finding. span=72782dd870b0

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Duplicate of TurnBlock placement — fixed in 82f14fe: the finished / lastReplyAt maps and the out.splice placement are removed; the filter is one pass again. Why TurnBlock's fold cannot draw these rows: a crewmate chat filters (finished silent turns) or folds (filterCrewmateChat) its tool rows before ChatMessageList groups turns, so TurnBlock's tool fold never receives a tool row on this surface; the steps line reuses its pages.chat.turnBlock.worked_through_step summary and the same tool line and thinking block instead. span=0aef3e1abc1d

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 8, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Controls read correctly, but only as a guess — rebutted: both were read correctly; the line carries a chevron, aria-expanded, and the same "Worked through N steps" wording the ordinary turn fold already uses, so it reads like the control readers know from every other chat. The finished-turn line is gone in c9aeadc. span=f2612886e2e6

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Indent opened rows past the chevron — fixed in c9aeadc: the opened list is indented pl-5, past the chevron, so the rows read as the line's children. span=1b69b3a791b2

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Pre-tool streaming row marks running steps finished — fixed in c9aeadc: a trailing streaming row in the running turn is held and drawn after the live line instead of ending the live run. Test: "a streaming row the store parked below the tool rows does not end the live run". span=df18ddb850d3

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 9, 2026
…iet finished summary

A crewmate's live tool/thinking rows now draw as ONE collapsed line: a pulsing mark, the current step's title and the step count; the pane's working footer hides while it is the newest row. A finished turn the crewmate spoke in keeps a quiet 'Did N steps' line. Both open on click or Enter (aria-expanded) to the ordinary tool line and thinking rows. Ordinary chats are unchanged.
@iamwhatever
iamwhatever force-pushed the feat/crewmate-work-line branch from c9aeadc to 98bebed Compare October 9, 2026 00:55
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 9, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Use the shared button primitive — fixed in 98bebed: the steps-line disclosure is now the shared Btn from components/ui, flattened to a text line with border-transparent bg-transparent overrides; aria-expanded / aria-controls kept. span=4a54df67ef06

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Footer shows while a streaming row is parked below the tools — fixed in 98bebed: ChatPane stands the footer down when ANY row is the live steps line, not only the last. Test "text streamed before the tools (parked below them) keeps the live line and still no footer" fails against the last-row check. span=8a176cb76d59

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Footer check reads the last row — fixed in 98bebed: same change as span 8a176cb76d59, pinned by the ChatPane.crewmate test the Clears-when names. span=0a037a5004f5

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Narrow title is still cut off — fixed in 98bebed: no clamp below sm; the title wraps in full (break-words, sm:truncate). The 320px shot shows the whole title on three lines. span=42658a859ac0

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Opened heading repeats the last step — fixed in 98bebed: open, the heading shows only "N steps"; the running row below (spinning) is the only place the current step appears. span=1c401c7667e3

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Open heading: count only — fixed in 98bebed: took this suggestion as written. span=11e2e0e759de

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • "Worked through 1 step" read as a guess — rebutted: the reader identified it correctly; it is the exact pages.chat.turnBlock.worked_through_step wording every ordinary chat already uses for folded steps, with a chevron and aria-expanded. The counts differ across shots because they are different turns (one earlier run of 1 step, then the live run of 2). span=eb691e7b4a58

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Thinking-only runs dropped mid-turn is undeclared — fixed in the PR description: "such an earlier run with no tool call (thinking only) has no step to count and is dropped" is now stated in What changed. No code change; the newest (live) run is never dropped. span=b7a20b04d752

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Disclosure looks like an action button — rebutted: the title is the slot's own live tool status, the same words the sessions sidebar and the crew roster pill already show for this moment (toolStatusLabel); the line carries a chevron, aria-expanded, and a spinning ring, and is the shared Btn flattened to text. Rewording every agent purpose into a progress form is new copy logic outside this PR's goal. span=a56cfb175607

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Step count reads as a running total — rebutted: each line counts the steps it folds, and opens to exactly that many rows, so the number always matches what the line holds; a turn-wide total would claim rows the line does not contain. Lines only split when the crewmate speaks between them, and all fold away when the turn ends. span=660ebdb24e34

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Count drifts away on narrow screens — rebutted as non-blocking: at 320px the count sits on the same button, vertically centred beside the wrapped title, which keeps the whole title readable (the prior round's BLOCK). The opened rows are the ordinary ToolCallLine, whose truncation is that component's existing behaviour on every chat and out of this PR's scope. span=9afcd5f7af82

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Count first, title as status — rebutted: same reason as span a56cfb175607; the title is the shared live-status string, and reordering to count-first would make the live line disagree with the sidebar/roster line for the same moment. span=0d63c05a4f83

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Wrap the count inline after the title — rebutted as non-blocking: an inline count would wrap onto the title's last line at some widths and not others; the pinned count keeps one place for it at every width. Answered with span 9afcd5f7af82. span=51f44e4455ba

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Key moves from a thinking row to the first tool row — accepted as-is: only a line the user opened while the run held ONLY thinking (count 0, a "Thinking" heading) can close when the first tool call arrives; keying on the first tool call is what keeps every line with steps stable as steps arrive, which is the common path. The window is the seconds before the first tool call of a run. span=df18ddb850d3

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Oct 9, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #18256 (merged), which ships the owner-ruled shape from #18238: one status line for the crewmate's current step beside a still working indicator, nothing after the turn. This PR's expandable steps line conflicts with that ruling.

@iamwhatever iamwhatever closed this Oct 9, 2026
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 9, 2026
@iamwhatever
iamwhatever deleted the feat/crewmate-work-line branch October 9, 2026 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge conflict Branch has merge conflicts with its base — author must resolve before merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant