Dave Reid

I think this is a duplicate of https://github.com/cweagans/composer-patches/issues/376 but there's possibly an older issue tracking this too. It's kind of known that generally doing a `composer update --lock` after the...

Well the problem is when that project that needs to have the additional patch **isn't updated** in the composer update as per https://github.com/cweagans/composer-patches/issues/376 and https://github.com/cweagans/composer-patches/issues/411

Not being able to see the patches in the committed lock file worries me a lot, because it adds a layer of uncertainty that your local might be different from...

Just a heads up that there's lots of documentation that when you change patches in your composer.json file, we've been always advised to run `composer update --lock` to get the...

Not sure about Github Actions redirecting to the correct one, likely we'd need to update existing references, but I'm not 100% certain on that. +1 to moving under the drud...

According to https://github.com/github/docs/issues/15575 we should probably just create a new repository and archive the old one.

> Note: GitHub will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error repository not found. Instead,...

Yeah, I'm also seeing that when installing DDEV manually in Github Actions that `ddev auth ssh` doesn't work as expected in CI: ``` Run ddev auth ssh the input device...

I'm going to try the following instead, which *would* allow me to use this action as normal: ```yaml - name: Setup the Pantheon SSH key to be available to DDEV...

Ah, so I found that it's this line in the default pantheon.yaml source file: ```yaml auth_command: command: | set -eu -o pipefail ssh-add -l >/dev/null || ( echo "Please 'ddev...