Andrew Berry
Andrew Berry
Here's the Dockerfile lines I used to bring this into a project. ``` # Install action-validator for GitHub actions linting. RUN /bin/bash -c '([[ $(arch) == "aarch64" ]] && curl...
I've marked this as high priority since we're talking about a 35x slowdown for real-world projects.
I'm calling this a bug for now, because I think we always intended these to be optional once upstream supported it.
While I think they should probably be off by default, individual projects can disable them with this in `composer.json`: ``` "file-mapping": { "[project-root]/.ddev/docker-compose.selenium.yaml": false }, ```
Related: Lullabot/drainpipe#503 .
I think this is probably easiest and fastest using drush's JSON output, rather than browsing and parsing the status report HTML page.
I think rather than storing a count, we could have a known-issues list that's committed to the repo, like we've done with security issues awaiting patches.
> like we've done with security issues awaiting patches. > @deviantintegral is this in the Drainpipe's repo? I don't think it is! @justafish do you think that makes sense to...
Solving this would also give users a way to work on and work around somewhat-bugs like https://github.com/Lullabot/drainpipe/issues/410.
Here's an example of a composer install task that automatically skips if composer is up to date: ``` override:drupal:composer: desc: Install composer dependencies summary: | This command is typically used...