Forgejo mobile notifications

Notifications should surface the work that needs a decision without turning the forge into a distraction feed.

Mobile

What this solves

You want useful mobile notifications from Forgejo activity.

Best fit

Review requests
Failed checks
Mentions
Approval follow-up

How to think about it

High-signal notifications are tied to ownership and decisions: review requested, check failed on your change, mention in an active discussion, or approval requested before release. Everything else should earn its place.

Notification tiers

Send immediately:
- Review requested
- Failed required check
- Direct mention

Batch or mute:
- General repository activity
- Successful routine runs
- Low-priority issue updates

Practical path

01 Start with high-signal events like review requests and failed checks.
02 Tune notification volume before inviting the whole team.
03 Keep incident and security alerts separate from routine repository activity.

When to choose another path

Start narrow and add event types only when people ask for them.

Separate operational incidents from repository collaboration notifications.

Review notification volume after the first week of team use.

Next resources

Fjord Mobile

Mobile product page.

Download on the App Store

Install Fjord Mobile for iPhone and iPad.

Mobile docs

Setup and usage guides.

Security review

Review trust and access model.

Managed hosting

A Forgejo instance operated for your team.