change(requests): closures are now handled by pkgbase actions

Browse source

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 <kevr@0cost.org>

...

This commit is contained in:

Kevin Morris 2021-12-09 20:27:40 -08:00

parent 26b1674c9e

commit 1fede8d2a3

No known key found for this signature in database

GPG key ID: F7E46DED420788F3

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show stats Download patch file Download diff file Expand all files Collapse all files

Diff content is not available