Create a patch for an issue page

I could unpublish that page. Would be that sufficient, or is there anything else that needs to be done to avoid that page is shown on https://www.drupal.org/community/contributor-guide/find-a-task → ?

(I agree with what proposed here: Patches should no longer be used to contribute, although some project maintainer seems to still be asking for a patch instead of a merge request.)

Should not this issue be extended to similar pages about patches like the following ones?

• Backport a patch →
• Create a Drupal 11 compatibility patch →
• Reroll a patch →

Other pages, like Review a patch or merge request → , could be edited to remove any reference to patches, but this is a different task, which should be probably postponed to when nobody is asking for patches in issues.

I don't think there is a reason to keep the outdated tasks unpublished, archived, or otherwise. I’ve deleted the task.

Some of the other tasks look good, but need to be updated for merge requests.

It is better to handle the other pages in different issues, since they must be evaluated separately. For example, Backport a patch is still a current task, but it should not describe what to do to get a patch from a merge request, since merge requests are supposed to be used nowadays.

Automatically closed - issue fixed for 2 weeks with no activity.