From 1fede8d2a308e9cdc16cb4024cb0d6a3bcdb0294 Mon Sep 17 00:00:00 2001 From: Kevin Morris Date: Thu, 9 Dec 2021 20:27:40 -0800 Subject: [PATCH] change(requests): closures are now handled by pkgbase actions Workflow has changed and TUs should now depend on actions taken closing requests which exist for the package base (deletion, merge, disown|orphan). The `/requests/{id}/close` route is now purely used for rejecting requests. The deletion, merge and orphan closures have been added into their related action routes. See the lists below. Disowning can only be done if an existing orphan request can be found for the action by TUs. Maintainers can disown their own packages at any time. Actions which provide request closures: -------------------------------------- - `/pkgbase/{name}/delete`: deletion request closure - `/pkgbase/{name}/merge`: merge request closure - `/pkgbase/{name}/disown`: orphan request closure To close a request: ------------------ - `/requests/{id}/close`: close a request with rejected status For deletion and merge actions, if no request yet exists, one will be autogenerated and closed. For orphan requests, a preexisting require is required and an error is now returned in cases where one cannot be found. For all closure actions, if the new comments field is left empty, a closure comment will be autogenerated. Note: This is a documentation commit summing up UX changes from recent commits. Signed-off-by: Kevin Morris