Notifications & Watch Settings

CodeFloe extends Forgejo’s notification system with granular watch settings, giving you fine-grained control over which repository events generate notifications.

Watching a Repository

When you watch a repository, you receive notifications for activity in that repository. The Watch dropdown on any repository page lets you choose exactly which events you care about.

Event Types

Each watch subscription is a combination of four independent event types:

Participating — Notifies you when you are @mentioned or when activity happens on issues/PRs you’ve participated in (commented, reviewed, or were assigned to).
Issues — Notifies you when issues are created, closed, or commented on.
Pull Requests — Notifies you when pull requests are created, merged, or commented on.
Releases — Notifies you when new releases are published. These appear as dedicated release notifications in your notification inbox.

Check any combination of these to build the subscription that fits your workflow!

Unwatch

Click Unwatch at the bottom of the dropdown to stop watching entirely. If you uncheck all event types and save, this has the same effect as unwatching.

Per-Repository Author Exclusions

The watch dropdown also includes an Excluded authors field. Add specific users here to suppress notifications generated by their actions on that repository. This is useful for filtering out bot activity (e.g., a CI bot that frequently comments on PRs) without losing notifications from human contributors.

Global Notification Settings

Your global notification preferences are configured under Settings > Notifications (/user/settings/notifications).

Email Notifications

Choose when to receive email notifications:

Enabled — Receive emails for all notifications.
And your own — Same as enabled, but also receive emails for your own actions.
On mention — Only receive emails when you are directly @mentioned.
Disabled — No email notifications.

Auto-Watch

Control when repositories are automatically added to your watch list:

On create — Automatically watch repositories you create.
On access — Automatically watch repositories when you first access them.
On contribute — Automatically watch repositories when you open an issue or pull request.

Default Watch Events

Set which event types are enabled by default when you start watching a new repository. These defaults apply both when you manually watch a repository and when auto-watch triggers.

For example, if you set your defaults to Issues and Participating, every newly watched repository will start with those two events enabled.

Global Author Exclusions

Two mechanisms let you suppress notifications from specific authors across all repositories:

Pattern — A comma-separated list of username patterns (supports * wildcards). For example, *-bot,renovate-bot would exclude any user whose name ends in -bot and the user renovate-bot.
User list — Search for and add specific users to globally exclude from your notifications.

How Notifications Are Delivered

Notifications appear in two places:

Web UI — The bell icon in the navigation bar shows your unread notification count. Click it to view and manage notifications. Release notifications have their own section.
Email — If email notifications are enabled and the instance has mail configured, you receive emails according to your email preference setting.

Interaction Between Settings

The notification system evaluates settings in this order:

Global author exclusion — If the acting user matches your exclusion pattern or user list, the notification is suppressed.
Per-repo author exclusion — If the acting user is in your per-repository exclusion list, the notification is suppressed.
Watch event type — Only events matching your enabled event types generate notifications.
Participating — When you are @mentioned or have participated in a thread, you receive a notification if you have Participating enabled (or if you aren’t watching the repo at all, in which case you still receive mention notifications as a default).
Email preference — Determines whether the notification also triggers an email.