Problem/Motivation

If a patch was made a long time ago, and needs to be rerolled, it's quite cumbersome to run the patch manually in order to see if it applies well, or to work out merge conflicts.

Steps to reproduce

  1. Go to https://www.drupal.org/project/drupal/issues/3167799
  2. Open DrupalPod with the patch from comment nr. 36
  3. That patch is faulty, but it seems to apply fine.

Proposed resolution

  1. When initializing DrupalPod with a patch that does not apply cleanly, give the user a warning that is obvious (right now you could technically see in the history of the console that a patch did not apply well, but I think many will miss that detail)
  2. Make all patches available in a directory (maybe outside the project dir, people can move the patches to the root of the project and apply them there using git) (although technically this could be solved using wget)

Remaining tasks

  1. Create warning message if a patch that was chosen for initialisation could not be applied correctly
  2. Add a directory with all patches of the issue to the workspace

Comments

colorfulCoder created an issue.