gitnex
/
GitNex
16
75
Fork 10
Code Issues 69 Pull Requests 2 Projects 0 Releases 40 Wiki Activity
Labels Milestones
New Issue

#888 Include state of issue/pull request in notifications list

Open
opened 2 weeks ago by opyale · 5 comments
opyale commented 2 weeks ago
Collaborator

Just tint the icons in a particular manner to indicate whether an issue is closed or a PR was merged

This will also require an update of the NotificationSubject model.

Just tint the icons in a particular manner to indicate whether an issue is closed or a PR was merged This will also require an update of the ``NotificationSubject`` model.
👍 1
opyale added the
Enhancement
label 2 weeks ago
opyale added the
UI/UX
label 2 weeks ago
opyale self-assigned this 2 weeks ago
6543 added the
API-dependency
label 2 weeks ago
6543 commented 2 weeks ago
Collaborator

Let me add this, I eventualy will get it into v1.14 but not for sure ...

Let me add this, I eventualy will get it into v1.14 but not for sure ...
6543 removed the
API-dependency
label 2 weeks ago
6543 commented 2 weeks ago
Collaborator

NotificationSubject does have a state field

`NotificationSubject` does have a `state` field
6543 commented 2 weeks ago
Collaborator

@opyale gitnex/tea4j#11

@opyale https://codeberg.org/gitnex/tea4j/pulls/11
🎉 1
6543 commented 2 weeks ago
Collaborator

state can be "", "closed", "open", and eventualy "merged" later ...

-> https://github.com/go-gitea/gitea/pull/15344

state can be "", "closed", "open", and eventualy "merged" later ... -> https://github.com/go-gitea/gitea/pull/15344
👍 1
opyale commented 2 weeks ago
Poster
Collaborator

@6543

state can be "", "closed", "open", and eventualy "merged" later ...

-> https://github.com/go-gitea/gitea/pull/15344

Would be nice, if this could be added to the API description. 🙂

@6543 >state can be "", "closed", "open", and eventualy "merged" later ... > >-> https://github.com/go-gitea/gitea/pull/15344 Would be nice, if this could be added to the API description. 🙂
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
7-assign-team-to-repo
master
release-3.5
release-1.1
release-1.2
release-1.3
release-1.4
release-1.5
release-2.0
release-2.1
release-2.2
release-2.3
release-2.4
release-2.5
release-3.0
release-3.1
release-3.2
release-3.3
release-3.4
Labels
Apply labels
Clear labels
Accepting-merge-requests API API-dependency Backport Blocked Brainstorming Breaking Bug Changelog CI Cleanup Confirmed Discussion Documentation Duplicate Enhancement External-dependecy F-droid Feature Frontport Good-First-Issue Google-play Has-backport Improvement Invalid Investigate Long-term Major-release Minor-release Needs-backport Needs-cleanup Needs-feedback Needs-help Performance Priority-critical Priority-high Priority-low Priority-medium Question Ready Refactor Regression Release Repository Security Suggestion Support Testing Translation UI/UX Upstream Website Wontfix
No Label
Accepting-merge-requests
API
API-dependency
Backport
Blocked
Brainstorming
Breaking
Bug
Changelog
CI
Cleanup
Confirmed
Discussion
Documentation
Duplicate
Enhancement
External-dependecy
F-droid
Feature
Frontport
Good-First-Issue
Google-play
Has-backport
Improvement
Invalid
Investigate
Long-term
Major-release
Minor-release
Needs-backport
Needs-cleanup
Needs-feedback
Needs-help
Performance
Priority-critical
Priority-high
Priority-low
Priority-medium
Question
Ready
Refactor
Regression
Release
Repository
Security
Suggestion
Support
Testing
Translation
UI/UX
Upstream
Website
Wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
 opyale
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes