Published an edit for a mod post may be seen as a new published post #119
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: degmods/degmods.com#119
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
I may have noticed that when publishing an edit, it might have been seen as a new published event / potentially seeing that on other clients as a new post?
After yesterday's discussion I believe this differs from client to client and how they're handling the editing and feed. We can keep it open until it's 100% confirmed that it's not something on our end.
So this is considered fixed, considering we've followed the documentation of the kind/nip standard on how to go about it, but apparently, depending on the client, it will still show this issue there.