the user must be able to set activity types for notification and the app then needs to poll in the background for activities of that type and if a new one shows up, send a notification to the user. touching the notification should open the app with that element belonging to that activity opened already. for example subscribing to issue created activities should open the created issue.
this is delayed for the public release, because it is more a polishing and also reliant on the dev account setup for publishing on the iOs app store.
the user must be able to set activity types for notification and the app then needs to poll in the background for activities of that type and if a new one shows up, send a notification to the user. touching the notification should open the app with that element belonging to that activity opened already. for example subscribing to issue created activities should open the created issue.
this is delayed for the public release, because it is more a polishing and also reliant on the dev account setup for publishing on the iOs app store.
hugo
added this to the first public update release milestone 2026-07-31 13:19:36 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
the user must be able to set activity types for notification and the app then needs to poll in the background for activities of that type and if a new one shows up, send a notification to the user. touching the notification should open the app with that element belonging to that activity opened already. for example subscribing to issue created activities should open the created issue.
this is delayed for the public release, because it is more a polishing and also reliant on the dev account setup for publishing on the iOs app store.
thinking about it: pointless, spammy and battery drain. if I am interested, I can look at the app or use the widget on the iphone.