Per-change Rules

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
django, python
Domain
backend

Research direction

Start by reviewing Patchwork's existing filepath-based auto-delegate feature and the linked mailing-list discussions. Compare the proposed rule types with Phabricator Herald, and read Django's reusable-app guidance before deciding whether this belongs in a separate application. The issue does not define an implementation scope or concrete completion criteria.

Written by the indexing model from the issue text.

Description

enhancement

Overview

The autodelegation feature provided in v1.1.0 offers a way to create filepath-based auto-delegate rules. However, there are reasons why we might want to expand this feature to cover other types of rules, as provided by tools like Phabricator Herald.

This was discussed previously on the mailing list and users of patchwork have discussed similar requirements.

If implemented, it might be a good idea to do so as a different application. This will ensure users can disable the application if not required. The linaro patchwork instance provides a good example on how to achieve this through their "patchmetrics" extensions.

Dependencies

None.

Additional Work Items

None.

Alternatives

  • We could keep the existing auto-delegate feature as-is and provide scripts using the XML-RPC API/REST API to implement this functionality
  • We could allow third-parties to add this functionality as required (like the auto-delegate feature).

Useful resources

Dominant language
Python
Stars
317
Forks
91
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.