[New] Notifications #5
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#5
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is dependent on Gitea API. Right now there is no API for it.
Created By: @lunny
Please send a feature request issue to gitea.
Older issue I found for this, https://github.com/go-gitea/gitea/issues/4811
https://developer.android.com/guide/topics/ui/notifiers/notifications ... hmm
check updates ...
... by pull
... by push (FCM)
... by push (own)
-> do it the pull way?
Thanks @6543.
I try to avoid FCM and any google related implementation. Otherwise I have to handle two different versions of the app for gplay and f-droid.
Other than that, if Gitea implement a push service. Will be nice, but I am not sure it will happen in near future.
There is an app for fediverse(Fedilab), I work with the developer as UX and he implemented notifications I guess without FCM(Google). It will be more work but good for future. And notifications will be not instant, but surely a little delay will not harm though.
So yeah, pull way is the only way to go with. But still have time to do this, so let's wait and see how the things will turn out.
@mmarif -> https://github.com/go-gitea/gitea/pull/9488 🎉
Wish it was part of 1.11 release. Is 1.11 in freeze?
This PR if completed can be part of it.
NO 1.11 is in freeze -> we will get notification support with gitea 1.12
and I also send a extend for mobile clienst: https://github.com/go-gitea/gitea/pull/9595
@mmarif at this point only realy needed features can go into 1.11 (the owners + maintainers must be for it ...)
Then it makes sense if it is feature freeze.
Looking forward to this PR. One of the feature users will love it.
PR is merged! Gitea >= 1.12.0 will support this api
https://github.com/go-gitea/gitea/pull/9595 is merged now
so we have a api endpoint to check if app should show new notifications!
GET /notifications/new
and the default github notification-api to manage the rest ...
@6543 This is great. Thank you for the awesome work. 👍
as @opyale mentioned its worth to have a look at https://developer.android.com/topic/libraries/architecture/workmanager/
and we should keep track of https://github.com/go-gitea/gitea/pull/10884 since it enable Web Push witch we perhaps could use in some way?
Web push may not work unless we use webview in the app kinda of think about Electron app on desktop.
Yes, workmanager is a good link.
Just one thing we need to make sure is to not use anything related to Google data saving like firebase(GCM) etc because we can't keep two separate apps for play store and f-droid. Also the core of this app is to be privacy friendly.
Any ideas which does not touch that ground are always welcome.
I can try to implement smth with workmanager.
@opyale That would be great, atleast a start on this. We can enhance or change to something else later on depends on the situation/implementation.