Skip to content

feat(sidebar): hide every PR and Issue chip from the session menu - #18556

Merged
iamwhatever merged 1 commit into
kirodotdev:mainfrom
Pearcekieser:feat/hide-all-session-chips
Oct 10, 2026
Merged

iamwhatever merged 1 commit into
kirodotdev:mainfrom
Pearcekieser:feat/hide-all-session-chips

Conversation

@Pearcekieser

@Pearcekieser Pearcekieser commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A user can hide every PR and Issue chip on a session from its right-click menu in one action, instead of one chip at a time.

The session menu's "Hide a PR or Issue chip" submenu hides one chip per two clicks. A long-running session collects 20 or more chips (a fleet worker that rebased across many PRs, a triage thread), so clearing its row takes 40 or more clicks through a scrolling list.

Why it matters

Chips on a stale session crowd the sidebar row and its strip wraps to several lines. The single-chip path makes clearing them tedious enough that users leave them, which keeps the sidebar noisy.

Not a goal

  • A backend bulk-dismiss endpoint. The existing per-link DELETE is reused as is.
  • Undoing a hide. There is still no un-dismiss route, as before.
  • Hiding chips across several sessions at once.

What changed (motivation → approach → change)

The submenu in website/src/components/SourceLinksSubmenu.tsx now starts with a "Hide all PR and Issue chips" entry, shown when the session has two or more chips. It uses the same two-step confirm as a single chip: the first select stages it ("Select again to permanently hide all 4 chips", with the count of chips it will hide), the second commits.

Committing walks the existing per-link DELETE one identity at a time. Each request carries the session generation captured at staging, so the backend's 409 guard refuses any request that would land on a replacement session, and the loop also stops locally once the live generation moves. The first refusal stops the walk and shows the existing "Could not hide" notice. I chose reuse over a new bulk endpoint because the per-link handler already owns the generation, rebind and persistence guards, and duplicating them for a bulk path would be a second copy of that logic.

On a session whose row shows only part of its chips, the entry stays disabled until the full list has loaded from the source-links read, and a placeholder list carried across a re-key does not count as loaded, so chips behind "+N" are included. While the walk runs every entry is disabled and the "hide all" entry reads "Hiding chip 2 of 6". It stays mounted until the walk ends so keyboard focus is not dropped. If a request fails partway, the existing error notice reads "Stopped after hiding 2 of 6 chips. The chips still listed were not hidden. Could not hide. Try again.", so the count reaches the notice's report and the agent hand-off, and the chips it did not reach stay listed. If the menu closes mid-walk, the walk still runs to the end, the same way a single committed hide finishes after the menu closes, and a reopened menu disables its entries while a DELETE is in flight. Staging a single chip clears an earlier walk's count. The four new strings are added to website/src/i18n/locales/en.manual.json, translated in every shipped catalog under website/src/i18n/locales/, and the en-XA.json pseudolocale is regenerated.

Backwards compatibility

Compatible: the single-chip entries and the DELETE contract are unchanged; the new entry only issues requests the single-chip path already issues.

Removes nothing: the diff adds a menu entry and two catalog keys and takes nothing away.

Tests

website/src/test/ChatSidebar.sourceLinkUnlink.test.tsx gains eight cases, seven tests with one run against both menus:

  • hide all through the dropdown and the context menu stages first, then sends one DELETE per chip in order, all with one generation, and removes every chip and the submenu
  • the DELETEs go one at a time, the entry reads "Hiding chip 1 of 2" while disabled, and the first failure stops the walk with the error notice and "Stopped after hiding 0 of 2 chips", leaving both chips
  • a failure on the second DELETE reports "Stopped after hiding 1 of 2 chips" and leaves only the chip it did not reach, and a later single-chip failure drops the count
  • on a truncated session the entry is disabled until the full list loads, then hides the off-preview chip too
  • a same-key session recreation drops a staged hide all without any DELETE
  • the entry stays mounted, reading "Hiding chip 2 of 2", while its walk is still running
  • a session with a single chip shows no hide all entry

Two keyboard tests now step past the new first entry with ArrowDown.

Manual verification

Ran the built SPA in Playwright against stubbed /api routes: right-click a session with four chips, open the submenu, select "Hide all" twice, and confirm four DELETEs and an empty chip strip, in dark and light themes. A second run used a truncated session with six chips, a held source-links read and a 503 on the third DELETE, to capture the loading, walking and stopped states.

Screenshots / video

The submenu with the new entry (dark):

Hide all entry at the top of the submenu

After the first select, staged for confirmation with the count (light):

Staged confirm

After the second select, the row has no chips (dark):

Row with no chips

A truncated session ("+2") before its full list loads, with the entry disabled and a spinner above it (dark):

Disabled until the full list loads

Mid-walk, the entry reads "Hiding chip 2 of 6" and every entry is disabled (light):

Walk in progress

The third DELETE failed: two chips are gone, the four it did not reach stay listed, and the error notice carries the count (dark):

Walk stopped by a failure

Related Issues

Fixes #18555

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

@Pearcekieser
Pearcekieser requested review from a team and KiroCrewCaptain as code owners October 9, 2026 18:45
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5, fork) — 🟡 CONCERNS

UX-level review of 75ac570b85f86ca115ed87b6727cfafbe645aefe via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

The partial-failure notice is four sentences that contradict each other, and no first-time reader has checked any of the new states.

Watch

  • The stopped notice says two opposite things. It joins hide_all_source_links_stopped onto unlink_source_link_failed. Screenshot 06 shows the result: "Stopped after hiding 2 of 6 chips. The chips still listed were not hidden. Could not hide. Try again." The user first reads that 2 chips were hidden, then reads "Could not hide." That is four sentences where the error copy limit is two. It also doesn't say how to retry: "Try again" can't mean re-picking chips one at a time, so the user has to work out that it means staging "Hide all" again. Someone hits this on every partial failure; it's rare, but it leaves them unsure what happened. Fix: when a walk stopped, show one string in place of both, e.g. "Hid 2 of 6 chips, then stopped. Select Hide all again to hide the other 4."
  • Nothing says why the entry is disabled while the list loads. Screenshot 04 shows a bare spinner over a greyed-out "Hide all PR and Issue chips", with no reason given. It only happens on truncated sessions and the wait is usually short, so this is low severity. Fix: while !listComplete, label the entry "Loading all chips…".

Suggestions

  • In hide_all_source_links_confirm, name what gets hidden: "Select again to permanently hide all {{count}} PR and Issue chips". This matches the idle label, so the staged state reads as the same action.

[UX-REVIEWED] 75ac570

Description read

[DESCRIPTION-READ] d2cffd2b43be298467a4c05b8e5f20b53c9395bb816e543bc69985bbfece1825

That sha256 names everything this verdict read: the PR description, plus the 9 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 9, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5, fork) — ✅ PASS

Design-level review of 75ac570b85f86ca115ed87b6727cfafbe645aefe via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check one case: if the menu closes mid-walk and reopens, the "Stopped after N of M" count is lost because the walk's state lives inside the submenu, which unmounts on close.

[DESIGN-REVIEWED] 75ac570

Description read

[DESCRIPTION-READ] b3cbbf276e6c510dfaaca0183bcb26c06ac317a1bdfcd15024ba6c3a2cbe2aa9

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 9, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5, fork) — 🟡 CONCERNS

Premise-level review of 75ac570b85f86ca115ed87b6727cfafbe645aefe via the fork AI-review pipeline — 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: CONCERNS

The "Stopped after hiding N of M chips" prefix brings in new state that has to be reset in three places, but the chips still listed already show what was left.

Not justified as shipped

  • Item 5 — oversized: the Goal is hiding every chip in one action, and the existing notice already reports the failure. The new prefix's own text says "The chips still listed were not hidden", so the list already answers what remains. To carry the count, walkStopped must be cleared in the sessionId effect, when "hide all" is staged and when a single chip is staged.
    Subtraction: delete walkStopped, its three resets, the ternary in message and the hide_all_source_links_stopped key in all 14 catalogs. Keep the plain unlink_source_link_failed notice.
    Clears when: the count is removed, or a linked report shows that a user who saw the remaining list still could not tell how far the walk got.

What this change ships

Inventory (7 items) — 6 justified

Intent: let a user clear every PR and Issue chip from one session in a single confirmed action instead of two clicks per chip. ADDITION (#18555).

  1. A new "Hide all PR and Issue chips" first entry in the submenu, shown with two or more chips, with a two-step confirm — justified
  2. The entry stays disabled on a truncated session until the full list has loaded — justified
  3. Every single-chip entry is disabled while the walk runs — justified
  4. The entry reads "Hiding chip N of M" during the walk and stays mounted — justified
  5. A failure notice gains "Stopped after hiding N of M chips" — oversized: the remaining list already shows this
  6. The existing chip entries move one arrow-key step down — justified
  7. Six screenshots committed under temp-screenshots/hide-all-chips/ — justified

[FIRST-PRINCIPLES-REVIEWED] 75ac570

Description read

[DESCRIPTION-READ] 78fb2d2de012c3f1cee8eb04e1474cfcaf6ad229694c6cd2d23cf6a385fb6cc1

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 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review (fork) — ✅ no blocking findings

Reviewed 75ac570b85f86ca115ed87b6727cfafbe645aefe via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 75ac570

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review (fork) — ✅ no blocking findings

Reviewed 75ac570b85f86ca115ed87b6727cfafbe645aefe via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 75ac570

@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
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from 7ae3110 to e61d113 Compare October 9, 2026 19:15
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Pushed e61d113 for the UX review on 7ae3110 and the design note.

issue (blocking): evidence gaps for the walk, loading and stopped states.
The PR description now has three more screenshots from the built SPA. A truncated session with "+2" shows the entry disabled while the full list loads. Mid-walk, the entry reads "Hiding chip 2 of 6" with every entry disabled. After a 503 on the third DELETE, two chips are gone and four stay listed.

issue (non-blocking): a partial failure said nothing about progress.
When a DELETE fails, the walk now records how far it got and the submenu shows "Stopped after hiding 2 of 6 chips. The chips still listed were not hidden." above the existing error notice. Two tests cover a stop after 0 of 2 and after 1 of 2.

suggestion (non-blocking): put the count in the confirm.
Applied. The confirm now reads "Select again to permanently hide all 4 chips", in every catalog. Languages where the noun has to agree with the number put the count in a form that avoids the agreement. The running entry is relabelled "Hiding chip N of M" in place of the spinner-only state.

note (non-blocking): the walk keeps sending DELETEs if the menu closes partway.
This is intended. A committed single-chip hide also finishes after the menu closes, and hide all is the same commit applied to each chip. The submenu's local busy state goes away on close, but a reopened menu reads in-flight DELETEs from the mutation cache, so its entries stay disabled while a request is running. Stopping on close would leave a committed action half done, with no way to see that from the reopened menu.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 9, 2026
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from e61d113 to f2b289a Compare October 10, 2026 00:15
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Pushed f2b289a for the round 2 findings on e61d113, plus the Frontend Tests (1) failure.

issue (blocking): GPT 6.1, errors-use-error-notice at SourceLinksSubmenu.tsx:368. Fixed. The stopped count is no longer a separate muted <p>. It is folded into the existing ErrorNotice message, so "Stopped after hiding 2 of 6 chips. The chips still listed were not hidden." now reaches the notice's report, its ID and the sibling hand-off. The stopped-state screenshot (06) is recaptured to match.

issue (non-blocking): Opus 5.5, a stale stopped count could attach to a later single-chip failure. Fixed. Staging a single chip now clears walkStopped, and a test covers a hide-all stop followed by a failed single-chip hide.

note (non-blocking): UX placement of the notice. Kept at the bottom of the submenu, which is where single-chip hide errors already render, so both failures read the same way.

note (non-blocking): UX, the stopped count rendered muted next to a red error. Resolved by the same ErrorNotice change, since the count is now part of the red notice.

suggestion (non-blocking): UX, a "Loading all chips" line while the full list loads. Deferred. The disabled entry already blocks the action until the list is complete, and the label would add a new key to 12 catalogs for a state that lasts one request.

chore: Frontend Tests (1) on e61d113. destructiveConfirm.test.ts requires every interpolated value in a confirm string to be quoted or exempt. hide_all_source_links_confirm used {{n}}, which is neither. It now uses {{count}}, which the test exempts as a plain number, in all 13 catalogs. src/i18n plus the sidebar unlink tests pass locally (774), along with tsc, eslint, the i18n check and the build.

@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from f2b289a to 2f14fc1 Compare October 10, 2026 00:45
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Rebased on main (adfd71b), no behaviour change. The diff-only SAST (Semgrep) scan on f2b289a flagged test/test_readiness_poll_gate_max_age_14857.py:83, which this PR does not touch. It came in from main because the branch sat on the older base d4c3a73. The rebase was clean, and the SourceLinksSubmenu and src/i18n tests pass locally (745).

@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 10, 2026
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

note (non-blocking): could a maintainer re-run three failed jobs on 2f14fc1? The fork cannot re-run them (gh run rerun needs admin rights). All other 86 checks pass, and none of the three touches this diff.

  • Dependency License Gate (run 38010417697) stopped with "Dependency review is not supported on this repository". Three other PRs failed the same job around 00:50 UTC, and later runs pass.
  • Sensitive Change Review (run 38010417673) logged "Could not read the PR from the API (CalledProcessError); re-run this job".
  • E2E (stub ACP backend, offline) (run 38010417693) failed one spec, member-memory.spec.ts:600, with "Target page, context or browser has been closed" after 16.9 minutes. That spec covers member memory editing, which this PR does not change. 325 other specs passed.

@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 10, 2026
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from 2f14fc1 to 6cf4585 Compare October 10, 2026 05:15
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention labels Oct 10, 2026
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from 6cf4585 to e82ee84 Compare October 10, 2026 07:46
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Rebased on main (8ce11f0), no behaviour change. Main gained 3 commits touching the 13 locale catalogs this PR edits, so the green run on 6cf4585 no longer covered them. The rebase was clean, and tsc, i18n:check and 745 tests (src/i18n plus SourceLinksSubmenu) pass locally on e82ee84.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 10, 2026
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from e82ee84 to 3499b25 Compare October 10, 2026 08:01
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Pushed 3499b25 for Build Wheel and both Build Desktop jobs on e82ee84. chore: the frontend build runs gen-ui-index --check, which hashes the locale catalogs into input_digest in src/kiro_crew/docs/ui-index.generated.json. That index landed on main in #18443, after this PR's earlier green run, so this PR's new catalog keys left the committed digest stale. Rebased on main (44180a0), which added more catalog keys, then regenerated the index with npm run gen:ui. Only the digest line changes. gen-ui-index --check, tsc, i18n:check and the src/i18n plus SourceLinksSubmenu tests pass locally.

@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from 3499b25 to 7ffae6f Compare October 10, 2026 08:15
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Pushed 7ffae6f for Build Wheel, both Build Desktop jobs and E2E (stub ACP backend, offline) on 3499b25. All four stopped at the same gen-ui-index --check step. CI builds the merge with main, and main had moved to d3f462f, whose own committed index predates the dictation sound setting from #17923. Rebased on d3f462f and regenerated src/kiro_crew/docs/ui-index.generated.json. The diff adds the notifications.sound-category-dictation entry with its 12 labels, plus the new digest. gen-ui-index --check, tsc, i18n:check and the src/i18n plus SourceLinksSubmenu tests pass locally.

thought (non-blocking): First Principles, item 5, the partial-failure count repeats what the remaining list shows. Kept. The list alone cannot tell a stop after 0 of 6 from a stop after 2 of 6 without the user remembering how many chips there were, and the count is one string inside the existing ErrorNotice, which GPT 6.1 required in round 2.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author

CI on 7ffae6f finished with 90 checks passing. Frontend Tests (3) failed one test, and Frontend Coverage Merge, Coverage Gate and PR Readiness failed after it. The failing test is src/guide/GuideLayer.test.tsx > "pressing the highlighted control on the last step finishes the guide, as Done does" (expected 2 reports, got 1). This PR does not touch that file, and the test passes 3 of 3 runs locally on the same head. The fork account cannot re-run jobs. Could a maintainer re-run the failed jobs on this run?

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 10, 2026
@Pearcekieser
Pearcekieser force-pushed the feat/hide-all-session-chips branch from 7ffae6f to 75ac570 Compare October 10, 2026 10:15
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Rebased on main (d32c084), no behaviour change. Main regenerated src/kiro_crew/docs/ui-index.generated.json, which conflicted with this PR's copy. I took main's file and re-ran npm run gen:ui, and the output matches main byte for byte, so this PR no longer changes that file. gen-ui-index --check, tsc, i18n:check and the src/i18n plus SourceLinksSubmenu tests pass locally on 75ac570. This run also replaces the re-run I asked for on 7ffae6f.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 10, 2026
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Ready to merge on 75ac570. All checks pass, readiness is passed, the PR is mergeable, and the green run is fresh against main (d32c084, no new commits). Every review finding has an answer above. The fork account cannot enable auto-merge, so could a maintainer merge it or arm auto-merge?

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adds a "Hide all PR and Issue chips" entry to the session menu so a session with many chips can be cleared in one confirmed action (issue #18555, tier:T2). I read SourceLinksSubmenu.tsx in full. The entry uses the same two-step confirm as a single chip. It walks the existing per-link DELETE one request at a time, each carrying the generation captured at staging. It also stops locally when the live generation moves or a request fails. It stays disabled until the complete list has loaded (a placeholder carried across a re-key does not count), so chips behind "+N" are included. No new backend path and no wider permission: every request is one the single-chip path already sends. The new tests cover ordering, the sequential walk, stops after 0 and 1 chips, a truncated list, a same-key recreation dropping a staged hide, focus retention and the one-chip case. The temp-screenshots PNGs are on a fork PR, where the repo rules allow committed evidence. All checks are green at 75ac570, and GPT, Opus and Design pass. Non-blocking: UX says the stopped notice reads contradictorily ("Stopped after hiding 2 of 6… Could not hide. Try again."). Rewording it to say what "try again" means (select Hide all again) would be a cheap follow-up. — crew-pr-reviewer

@iamwhatever
iamwhatever enabled auto-merge (squash) October 10, 2026 19:06
@iamwhatever
iamwhatever merged commit d3224a9 into kirodotdev:main Oct 10, 2026
104 checks passed
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 10, 2026
Pearcekieser added a commit to Pearcekieser/KiroCrew that referenced this pull request Oct 15, 2026
A stopped hide-all walk showed "Stopped after hiding 2 of 6 chips. The
chips still listed were not hidden." followed by the generic single-chip
"Could not hide. Try again.", which read as contradicting the count.
The stopped notice now ends with "To try again, hide the rest from this
menu." in all 13 catalogs. It names the menu rather than Hide all
because a single remaining chip removes that entry.

Follow-up to the review on kirodotdev#18556.
iamwhatever pushed a commit that referenced this pull request Oct 15, 2026
A stopped hide-all walk showed "Stopped after hiding 2 of 6 chips. The
chips still listed were not hidden." followed by the generic single-chip
"Could not hide. Try again.", which read as contradicting the count.
The stopped notice now ends with "To try again, hide the rest from this
menu." in all 13 catalogs. It names the menu rather than Hide all
because a single remaining chip removes that entry.

Follow-up to the review on #18556.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(sidebar): hide all PR and Issue chips from the session menu

2 participants