Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a patch is retested it is usually to confirm that it still applies against the current version of the codebase. On situations where the restest fails, it would be really useful if it would then automatically add the "Needs reroll" tag rather than requiring manual intervention.
Comments
Comment #1
YesCT CreditAttribution: YesCT commentedclarifying that reroll is only needed when a patch fails for failing to apply.
https://www.drupal.org/contributor-tasks/reroll
fixing a patch that has test failures, or drupal cannot install is not a reroll. What is needed then is an improved patch (with an interdiff).
https://www.drupal.org/node/2272209 (the tasks template source for the dreditor insert tasks button)
has something similar, but not the same as a task "make issue pass tests". I think we are mostly used to looking for needs work status for that.
<!-- <tr><td>Update the patch to incorporate feedback from reviews (include an <a href="https://www.drupal.org/documentation/git/interdiff">interdiff</a>)</td><td></td><td><a href="https://www.drupal.org/contributor-tasks/create-patch">Instructions</a></td><td></td></tr> -->