[PATCH 5/5] docs: Add delegation guide
stephen at that.guru
Wed Oct 12 05:01:51 AEDT 2016
We do autodelegation - let's tell people all about it.
Signed-off-by: Stephen Finucane <stephen at that.guru>
docs/usage/delegation.md | 35 +++++++++++++++++++++++++++++++++++
mkdocs.yml | 1 +
2 files changed, 36 insertions(+)
create mode 100644 docs/usage/delegation.md
diff --git a/docs/usage/delegation.md b/docs/usage/delegation.md
new file mode 100644
@@ -0,0 +1,35 @@
+Patchwork has the concept of patch delegation. Delegates are akin to reviewers,
+in that they are Patchwork users who are responsible for both reviewing a patch
+and setting its eventual state in Patchwork. Delegation works particularly well
+for larger projects where various subsystems, each with their own
+maintainer(s), can be identified.
+Autodelegation allows patches to be automatically delegated to a user based on
+the files modified by the patch. To do this, a number of rules can be
+configured in the project admininstration page. This can usually be found at
+**NOTE:** Autodelegation can only be configured by Patchwork administrators,
+i.e. those that can access the 'admin' panel. If you require configuration of
+autodelegation rules on a local instance, contact your Patchwork administrator.
+In this section there are the following fields:
+ <dd>A path in <a href="https://docs.python.org/2/library/fnmatch.html">
+ fnmatch</a> format. The fnmatch library allows for limited, Unix shell-style
+ <dd>The patchwork user that should be autodelegated to the patch</dd>
+ <dd>The priority of the rule relative to other patches. Higher values
+ indicate higher priority</dd>
+Rules should be configured by setting the above fields and saving the rules.
+These rules will be applied at patch parse time.
diff --git a/mkdocs.yml b/mkdocs.yml
index ceb57d9..72fb368 100644
@@ -18,3 +18,4 @@ pages:
- REST API: 'usage/rest.md'
- XML-RPC API: 'usage/xmlrpc.md'
- Hint Headers: 'usage/headers.md'
+ - Delegation: 'usage/delegation.md'
More information about the Patchwork