It's too easy to 'permanently' destroy items. On press, explain what it does and ask for confirmation.
It's not documented anywhere: where archived items go, and how could they be restored. → I think this + direct DB access is enough.
It's too easy to 'permanently' destroy items. On press, explain what it does and ask for confirmation.
It's not documented anywhere: where archived items go, and how could they be restored. → I think this + direct DB access is enough.
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.
It's too easy to 'permanently' destroy items. On press, explain what it does and ask for confirmation.
It's not documented anywhere: where archived items go, and how could they be restored. → I think this + direct DB access is enough.
Changing archival to a type of visibility now provides at least two clicks + the item doesn't go poof after editing (undo capability).