Highlight current user in signal suggested reviewers

[rafaeelaudibert]

Problem

When a signal report assigns suggested reviewers, it can be hard to tell at a glance whether you are on the list, and why. The commit SHA-only tooltip explaining the rationale isn't obviously discoverable — you have to know to hover.

Changes

In the Suggested reviewers section of the report detail pane:

• Sort the list so the current user appears first when present.
• For the current user, render a small info icon next to each commit SHA. The icon is the tooltip trigger, and the tooltip now has a "Why was I assigned?" title above the existing rationale, making the explanation discoverable.
• Other reviewers keep the existing behaviour (rationale tooltip on the SHA itself).

How did you test this?

• pnpm --filter code typecheck (web tsconfig)
• pnpm exec biome check on the edited file

Did not run the desktop app in this environment.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/inbox/components/detail/ReportDetailPane.tsx:826-840
When `isMe` is `true` but `commit.reason` is empty/null, the tooltip content is still a non-`undefined` `<Flex>` element (containing "Why was I assigned?" with a blank body), so hovering the SHA link will open an incomplete tooltip. The non-`isMe` branch already guards this with `|| undefined` — the same guard is needed here.

```suggestion
                              <Tooltip
                                content={
                                  isMe ? (
                                    commit.reason ? (
                                      <Flex direction="column" gap="1">
                                        <Text as="div" size="1" weight="bold">
                                          Why was I assigned?
                                        </Text>
                                        <Text as="div" size="1">
                                          {commit.reason}
                                        </Text>
                                      </Flex>
                                    ) : undefined
                                  ) : (
                                    commit.reason || undefined
                                  )
                                }
```

_{Reviews (1): Last reviewed commit: "Wrap commit SHA and info icon in a singl..." | Re-trigger Greptile}

[greptile-apps]

When isMe is true but commit.reason is empty/null, the tooltip content is still a non-undefined <Flex> element (containing "Why was I assigned?" with a blank body), so hovering the SHA link will open an incomplete tooltip. The non-isMe branch already guards this with || undefined — the same guard is needed here.

Suggested change

	<Tooltip
	content={
	isMe ? (
	<Flex direction="column" gap="1">
	<Text as="div" size="1" weight="bold">
	Why was I assigned?
	</Text>
	<Text as="div" size="1">
	{commit.reason}
	</Text>
	</Flex>
	) : (
	commit.reason || undefined
	)
	}
	<Tooltip
	content={
	isMe ? (
	commit.reason ? (
	<Flex direction="column" gap="1">
	<Text as="div" size="1" weight="bold">
	Why was I assigned?
	</Text>
	<Text as="div" size="1">
	{commit.reason}
	</Text>
	</Flex>
	) : undefined
	) : (
	commit.reason || undefined
	)
	}

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/inbox/components/detail/ReportDetailPane.tsx
Line: 826-840

Comment:
When `isMe` is `true` but `commit.reason` is empty/null, the tooltip content is still a non-`undefined` `<Flex>` element (containing "Why was I assigned?" with a blank body), so hovering the SHA link will open an incomplete tooltip. The non-`isMe` branch already guards this with `|| undefined` — the same guard is needed here.

```suggestion
                              <Tooltip
                                content={
                                  isMe ? (
                                    commit.reason ? (
                                      <Flex direction="column" gap="1">
                                        <Text as="div" size="1" weight="bold">
                                          Why was I assigned?
                                        </Text>
                                        <Text as="div" size="1">
                                          {commit.reason}
                                        </Text>
                                      </Flex>
                                    ) : undefined
                                  ) : (
                                    commit.reason || undefined
                                  )
                                }
```

How can I resolve this? If you propose a fix, please make it concise.

[rafaeelaudibert]

Should be inverse and just check for commit.reason before, right

[k11kirky]

should hoist check

content={
  commit.reason
    ? isMe
      ? (
          <Flex direction="column" gap="1">
            <Text as="div" size="1" weight="bold">Why was I assigned?</Text>
            <Text as="div" size="1">{commit.reason}</Text>
          </Flex>
        )
      : commit.reason
    : undefined
}

[k11kirky]

non blokcing approve, with an added suggestion for the greptile comment

[k11kirky]

should hoist check

content={
  commit.reason
    ? isMe
      ? (
          <Flex direction="column" gap="1">
            <Text as="div" size="1" weight="bold">Why was I assigned?</Text>
            <Text as="div" size="1">{commit.reason}</Text>
          </Flex>
        )
      : commit.reason
    : undefined
}

[k11kirky]

lol - didnt see the auto merge @rafaeelaudibert optional follow up in comments