Add notifications subcomand #148
No reviewers
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#148
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/tea:feat_notifications"
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?
close partly #90
note: #90 (comment) - at the moment only unread are supported
when go-sdk v0.12.2 will be released we can enhance this feature
But notifications is too long, maybe we need a
tea alias
command or we can changenotifications
tomessages
?@lunny
news
is short aliasBut I think
news
have different meaning fromnotifications
.suggestions are welcome :)
@lunny I think notifications is OK because that is what they are called everywhere else. It wouldn't be worth making it a few char shorter if people always have to remember what the different word we use is.
It also makes it very clear what the command does -- messages and news are not as clear what they do: are they direct messages from other users? news about the gitea instance?
LGTM but I think it doesn't need the news alias since it makes it more confusing that news and notifications would be the same thing.
Maybe you will want news for something else latter too -- like what if a Gitea admin could post news about the site for all users to see? like "We've updated to a new version with these features..." or "We've changed the repository limit please see our blog post.."
I'll leave it unmerged for some more time - if I got a good idear for a short alias