Notifications dashboard

docs/astro.config.mjs

@@ -74,6 +74,7 @@ export default defineConfig({
             "configuration/searching",
             "configuration/pr-section",
             "configuration/issue-section",
+            "configuration/notification-section",
             "configuration/repo-paths",
             "configuration/keybindings",
             "configuration/theme",

docs/src/content/docs/configuration/defaults.mdx

@@ -10,6 +10,7 @@ settings on a per-section basis.
 ```yaml
 defaults:
   issuesLimit: 20
+  notificationsLimit: 20
   prApproveComment: LGTM
   preview:
     open: true
@@ -22,7 +23,7 @@ defaults:
 By default, the dashboard is configured to:
 
 - Display the preview pane with a width of 50 columns for all work items.
-- Only fetch 20 PRs and issues at a time for each section.
+- Only fetch 20 PRs, issues, and notifications at a time for each section.
 - Display the PRs view when the dashboard loads.
 - Refetch PRs and issues for each section every 30 minutes.
 - Display dates using relative values.
@@ -110,6 +111,21 @@ This setting defines how many issues the dashboard should fetch for each section
 [refresh current section]: /getting-started/keybindings/global/#r---refresh-current-section
 [refresh all sections]: /getting-started/keybindings/global/#r---refresh-all-sections
 
+### Notifications Fetch Limit (`notificationsLimit`)
+
+| Type    | Minimum | Default |
+| :------ | :-----: | :-----: |
+| Integer |    1    |   20    |
+
+This setting defines how many notifications the dashboard should fetch when:
+
+- The dashboard first loads.
+- You navigate to the next notification in a table without another fetched notification to display.
+- You use the [refresh current section] or [refresh all sections] commands.
+
+[refresh current section]: /getting-started/keybindings/global/#r---refresh-current-section
+[refresh all sections]: /getting-started/keybindings/global/#r---refresh-all-sections
+
 ### Preview Pane (`preview`)
 
 These settings define how the preview pane displays in the dashboard. You can specify

docs/src/content/docs/configuration/examples.mdx

@@ -31,6 +31,24 @@ issuesSections:
   - title: "Involved"
     filters: "is:open involves:@me -author:@me"
 
+notificationsSections:
+  - title: "All"
+    filters: ""
+  - title: "Created"
+    filters: "reason:author"
+  - title: "Participating"
+    filters: "reason:participating"
+  - title: "Mentioned"
+    filters: "reason:mention"
+  - title: "Review Requested"
+    filters: "reason:review-requested"
+  - title: "Assigned"
+    filters: "reason:assign"
+  - title: "Subscribed"
+    filters: "reason:subscribed"
+  - title: "Team Mentioned"
+    filters: "reason:team-mention"
+
 pager:
   diff: less
 showAuthorIcons: true
@@ -52,6 +70,7 @@ defaults:
     width: 84
   prsLimit: 20
   issuesLimit: 20
+  notificationsLimit: 20
 
 theme:
   ui:

docs/src/content/docs/configuration/layout/options.mdx

@@ -4,8 +4,9 @@ title: Valid Options
 
 ## Valid Layout Options
 
-Any column can define the [`grow`], [`width`], and [`hidden`] options.
+Any column can define the [`align`], [`grow`], [`width`], and [`hidden`] options.
 
+[`align`]: #column-alignment
 [`hidden`]: #hide-column
 [`grow`]: #grow-column
 [`width`]: #column-width
@@ -42,4 +43,26 @@ font to be monospace, this is a reliable way to ensure a minimum width for reada
 | `hidden` | boolean | false   |
 
 Specify whether the column should be hidden from view. Set this value to `true` to hide the
-column or `true` to show it.
+column or `false` to show it.
+
+## Column Alignment
+
+| Property | Type   | Default |
+| :------- | :----- | :------ |
+| `align`  | string | `left`  |
+
+Specify the horizontal alignment of the column's content. Valid values are:
+
+- `left` — Align content to the left (default)
+- `right` — Align content to the right
+- `center` — Center the content
+
+This is useful for numeric columns like comment counts where right-alignment improves readability.
+
+```yaml
+prs:
+  layout:
+    numComments:
+      width: 5
+      align: right
+```

docs/src/content/docs/configuration/notification-section.mdx

@@ -0,0 +1,135 @@
+---
+title: Notification Sections
+---
+
+# Notification Section Options (`notificationsSections`)
+
+Defines sections in the dashboard's Notifications view.
+
+- Every section must define a [`title`] and [`filters`].
+- When you define [`limit`] for a section, that value overrides the
+  [`defaults.notificationsLimit`] setting.
+
+[`title`]: #notification-title-title
+[`filters`]: #notification-filters-filters
+[`limit`]: #notification-fetch-limit-limit
+[`defaults.notificationsLimit`]: /configuration/defaults/#notifications-fetch-limit-notificationslimit
+
+## Search Section
+
+The Notifications view includes a search section (indicated by a magnifying glass icon) as the first tab. This serves as a scratchpad for one-off searches without modifying your configured sections.
+
+- Default filter: `archived:false`
+- Respects `smartFilteringAtLaunch`: when enabled and running from a git repository, the search automatically scopes to that repo
+- Use the `/` key to focus the search bar and enter custom queries
+
+## Default Sections
+
+By default, the dashboard includes these notification sections:
+
+```yaml
+notificationsSections:
+  - title: All
+    filters: ""
+  - title: Created
+    filters: "reason:author"
+  - title: Participating
+    filters: "reason:participating"
+  - title: Mentioned
+    filters: "reason:mention"
+  - title: Review Requested
+    filters: "reason:review-requested"
+  - title: Assigned
+    filters: "reason:assign"
+  - title: Subscribed
+    filters: "reason:subscribed"
+  - title: Team Mentioned
+    filters: "reason:team-mention"
+```
+
+You can customize these by defining your own `notificationsSections` in your config file.
+
+## Notification Title (`title`)
+
+This setting defines the section's name. The dashboard displays this value in the tabs for
+the Notifications view.
+
+## Notification Filters (`filters`)
+
+This setting defines the filters for notifications in the section's table. Notification filters differ from PR and Issue filters because they use client-side filtering.
+
+### Available Filters
+
+#### Read State Filters
+
+| Filter | Description |
+|--------|-------------|
+| `is:unread` | Show only unread notifications |
+| `is:read` | Show only read notifications |
+| `is:all` | Show both read and unread notifications |
+| `is:done` | Show archived/done notifications |
+
+#### Reason Filters
+
+| Filter | Description |
+|--------|-------------|
+| `reason:author` | Activity on threads you created |
+| `reason:comment` | Someone commented on a thread you're subscribed to |
+| `reason:mention` | You were @mentioned |
+| `reason:review-requested` | Your review was requested on a PR |
+| `reason:assign` | You were assigned |
+| `reason:subscribed` | Activity on threads you're watching |
+| `reason:team-mention` | Your team was @mentioned |
+| `reason:state-change` | Thread state changed (merged, closed, etc.) |
+| `reason:ci-activity` | CI workflow activity |
+| `reason:participating` | Meta-filter that expands to: author, comment, mention, review-requested, assign, state-change |
+
+#### Repository Filters
+
+| Filter | Description |
+|--------|-------------|
+| `repo:owner/name` | Show notifications only from the specified repository |
+
+### Filter Examples
+
+```yaml
+# Show only notifications where you were mentioned
+- title: Mentioned
+  filters: "reason:mention"
+
+# Show unread notifications from a specific repo
+- title: My Project
+  filters: "is:unread repo:myorg/myproject"
+
+# Show notifications where you're actively participating
+- title: Participating
+  filters: "reason:participating"
+
+# Combine multiple reason filters
+- title: Review & Mentions
+  filters: "reason:review-requested reason:mention"
+```
+
+### Filter Behavior
+
+- **Default behavior**: With no filters or empty filters, the section shows unread notifications plus any bookmarked notifications
+- **Explicit `is:unread`**: Shows only unread notifications, excluding bookmarked read notifications
+- **Reason filters**: Applied client-side after fetching from GitHub's API
+
+## Notification Fetch Limit (`limit`)
+
+| Type    | Minimum | Default |
+| :------ | :-----: | :-----: |
+| Integer |    1    |   20    |
+
+This setting defines how many notifications the dashboard should fetch for the section when:
+
+- The dashboard first loads.
+- You navigate to the next notification in a table without another fetched notification to display.
+- You use the [refresh current section] or [refresh all sections] commands.
+
+This setting overrides the [`defaults.notificationsLimit`] setting.
+
+[refresh current section]: /getting-started/keybindings/global/#r---refresh-current-section
+[refresh all sections]: /getting-started/keybindings/global/#r---refresh-all-sections
+[`defaults.notificationsLimit`]: /configuration/defaults/#notifications-fetch-limit-notificationslimit

docs/src/content/docs/configuration/theme.mdx

@@ -41,6 +41,7 @@ colors:
     faint: "#8a8a8a"
     warning: "#800000"
     success: "#008000"
+    actor: "#c6c6c6"
   background:
     selected: "#808080"
   border:
@@ -212,6 +213,18 @@ dashboard UI:
 - The icon for passing checks for PRs in the preview pane
 - Success messages for commands, like when the dashboard fetches work items.
 
+#### Actor Text Color
+
+| Property | Type | default                                   |
+| :------- | :--- | :---------------------------------------- |
+| `actor`  | hex  | `#c6c6c6` for dark or `#808080` for light |
+
+This setting determines the color of the text for the following elements in the
+dashboard UI:
+
+- The username of the person who triggered a notification, displayed after the
+  notification title in the notifications view
+
 ### Background Colors (`background`)
 
 Defines the background colors for the dashboard. By default, the background color for