Inbox

The Inbox at /inbox shows the items that need your attention on one page. It replaces Forgejo’s separate issue, pull request and notification dashboards, and adds batch actions and keyboard shortcuts. Open it from Inbox in the top bar.

Tabs

The Inbox has three tabs. The address includes the current tab, such as /inbox?tab=pulls, so you can bookmark a tab.

Tab	Address	What it lists
Issues	/inbox?tab=issues	Issues, grouped into sections
Pull requests	/inbox?tab=pulls	Pull requests, grouped into sections
Notifications	/inbox?tab=notifications	All your notifications, newest first

A badge on each tab counts its items. The Notifications badge also sets the unread count in the top bar.

Sections on the Issues tab

The Issues tab sorts issues into four sections, in this order:

1. Assigned to you
2. Mentioning you
3. Created by you
4. Other unread: issues with an unread notification that fit none of the sections above, such as issues in a repository you watch.

An issue shows only in the first section it fits. An issue that is assigned to you and mentions you shows under Assigned to you only.

Sections on the Pull requests tab

The Pull requests tab has four sections:

1. Needs your action: pull requests where someone requested your review, that are assigned to you, or that you opened and that need your work. A pull request you opened needs your work when a reviewer’s latest review requests changes, or when its latest commit has a failing or erroring status. A label on each row says why, such as review requested, assigned, changes requested or CI failing, and the row shows how many approvals the pull request has.
2. Your open PRs, waiting on others: pull requests you opened that need nothing from you.
3. Mentioning you
4. Other unread

As on the Issues tab, a pull request shows only in the first section it fits.

Section limits

Sections list issues from repositories you can read, the same set as Forgejo’s issue dashboard. They skip archived repositories, except Other unread, which keeps unread notifications from archived repositories.

Each section shows 10 rows at first, or 25 for the first section, with Show more to load the next rows. Arbinel considers at most 500 matching issues per section. When a section matches more, the page says that counts are capped at 500 per filter.

Notifications tab

The Notifications tab lists your notifications on issues, pull requests and repositories, together with release notifications. Choose Unread, Pinned or All to filter the list.

Filters

The Issues and Pull requests tabs have three filters. The Notifications tab has none apart from Unread, Pinned and All.

Filter	What it does
Filter by text…	Matches the text you type, as in the issue search.
All owners	Limits the list to repositories of the user or organization you name. If no such user or organization exists, the page says so under the field and keeps the current list.
State	Open (the default), Closed or All. The Other unread section ignores it.

The text fields apply after you stop typing. When nothing matches, select Clear filters to go back to all open items.

Advanced filters opens Forgejo’s issue, pull request or notification page for the current tab, with all its filters. Subscriptions opens the list of issues and repositories you subscribed to, at /notifications/subscriptions.

Act on items

Each row has buttons to mark it read or unread and to pin or unpin it. A row on the Issues or Pull requests tab without a notification still has these buttons, and using one creates the notification first. Pinned rows keep their pin until you unpin them, and unpinning marks a notification read.

Batch actions

On the Issues and Pull requests tabs, select the checkbox of unread rows, then select Mark read in the bar that appears. Mark section read in a section header marks all the section’s shown unread rows read. When the section has more rows than it shows, the button says Mark shown read instead.

On the Notifications tab, select rows or Select all, then select Mark read, Mark unread, Pin or Unpin. Each action applies only to the selected rows it fits. Mark read and Mark unread do not change pinned rows, and release notifications cannot be pinned.

After you mark several rows read at once, Undo stays on screen for 10 seconds.

Mark all notifications read

Mark all read marks every unread notification read, including those your filters hide. It asks you to select it a second time to confirm, and it has no undo.

Keyboard shortcuts

Press ? on the Inbox to show the shortcuts, or select the keyboard button above the list.

Key	Action
j	Next row
k	Previous row
x	Select the row
e	Mark the row read or unread
p	Pin or unpin the row
Enter	Open the row
?	Show or hide the list of shortcuts
Esc	Close the list of shortcuts, cancel Mark all read, or clear the selection

The shortcuts do nothing while you type in a text field, or when you hold Ctrl, Alt or the Command key. To turn the single-key shortcuts off, clear Use single-key shortcuts in the list of shortcuts. Your browser remembers the choice, and Esc keeps working.

Live updates

The Inbox reloads its lists when you return to the browser tab, at most every 30 seconds. When the instance has [realtime] ENABLED = true, the Inbox also updates as soon as a notification arrives or a check changes.

Redirects from Forgejo addresses

/issues, /pulls and /notifications redirect to the matching Inbox tab. They redirect only without a query string, so /issues?page=1 still opens Forgejo’s issue dashboard. Advanced filters uses these addresses.

Differences from Forgejo

Forgejo has separate dashboards for issues, pull requests and notifications, each filtered by one relation to you at a time. Arbinel keeps them under the addresses above and adds the Inbox, which:

• shows all relations at once, as ranked sections,
• adds a Needs your action section for pull requests,
• lists release notifications with the others,
• adds batch actions, undo and keyboard shortcuts.