Travis Carden

@localheinz Which property paths should be added to the hardcoded exclusions? Off the top of my head I know of the following order-dependent paths: * [`extra.patches`](https://github.com/cweagans/composer-patches) is the one specifically...

Thanks for looking, @BanzaiMan. I should've linked to a build, too, illustrating the reported behavior. Here's one: https://travis-ci.org/github/acquia/drupal-spec-tool/jobs/664565141#L914

Closing as essentially "solved". [php-tuf/composer-stager](https://github.com/php-tuf/composer-stager) has been stable for some time now.

Note: Some of my step definitions have been released on Packagist as part of a specification tool we've created at Acquia: https://packagist.org/packages/acquia/drupal-spec-tool. See the [announcement blog post on the Acquia...

* Related: https://github.com/ergebnis/phpstan-rules/issues/77

@localheinz++ 😄

_I_ know _nothing_ about it. 🙂 I'll do some research after I finish with higher priorities.

- Fixed `trusted_host_patterns` error on Tugboat: https://github.com/phenaproxima/starshot-prototype/commit/cdb478a4f52d1df25db01c47369d32fddbdbfb8f. - Fixed rebuild access enabled error on Tugboat: https://github.com/phenaproxima/starshot-prototype/compare/5414fa9a...c1802404. - Turns out Webform module provides a Drush command to install the external libraries....

> Our code standards forbid throws tags since they quickly become stale. Where is this, @danepowell? I support making our example PhpStorm profile match our standards, though in the long...

Ah, I see. Well, I _personally_ would allow `@package` and `@throws` (though I would hardly make a fuss of them), but I can definitely support the others. We'll definitely want...