Create 2023-05-01-customize-your-openmage.md

[colinmollenhour]

A blog post to help users with a common need that is probably a lot easier than most people realize.

[sreichel]

Line can be removed. Was added as dev-req with zf1f.

[colinmollenhour]

Hmm, it was necessary when I tried it.. I think to use it in a project which has openmage as a dependency I think it is still required because dev dependencies of packages are not installed by default. The guide is written for users which would be using openmage as a dependency, not the openmage devs.

[sreichel]

The image should be (automatically) resized?

[ADDISON74]

A very good documentation but it requires some changes in format and information.

1. All PRs have a patch that can be downloaded as mentioned in the article by adding .patch at the end of the URL. If you look inside the file, there are conversations, changes/commits made over time. I recommend to edit these files and keep only the final changes before merging. For this reason it was strongly recommended over the years not to do PRs that modify a lot of files solving several issue in one place.

2. If someone is using the DDEV environment, the command to run vendor patches is ddev exec vendor/bin/vendor-patches generate.

3. Using the dry run option before patching.

[ADDISON74]

This change doesn't work in my case. My opinion there are missing steps.

{
  "...": "...",
  "extra": {
    "patches": {
      "openmage/magento-lts": {
        "Added form key validation to Contacts form #3146": "https://github.com/OpenMage/magento-lts/pull/3146.patch"
      }
    }
  }
}