Explore >> Select a destination
|
You are here 
|
mikemadison.net | ||
| | | | |
tomasvotruba.com
|
|
| | | | | [Composer 2 was released](https://twitter.com/packagist/status/1319945203797708800) this week. It brings **massive `composer install/update` performance** improvement of [150-200 %](https://blog.packagist.com/composer-2-0-is-now-available). That means [faster feedback](/blog/2020/01/13/why-is-first-instant-feedback-crucial-to-developers/) from CI and faster monorepo testing. Today, we'll look on how to use Composer in Github Actions with monorepo split testing and what to avoid. | |
| | | | |
daniel-siepmann.de
|
|
| | | | | The composer package "maglnet/composer-require-checker" allows you to check whether all used dependencies are actually registered via composer. | |
| | | | |
blog.bitexpert.de
|
|
| | | | | Automate and simplify the process of applying patches to your project files during the Composer install procedure with cweagans/composer-patches and symplify/vendor-patches. | |
| | | | |
gist.github.com
|
|
| | | Azure Functions - Part 4: Working with Persistent Data and Visual Studio Code - 1 - afp4_1.cs | ||
