Explore >> Select a destination
|
You are here 
|
sitr.us | ||
| | | | |
unwiredcouch.com
|
|
| | | | | ||
| | | | |
tomasvotruba.com
|
|
| | | | | In a post from autumn, we looked at how to [develop packages in monorepo on PHP 8.1 and release a downgraded version on PHP 7.2](/blog/how-to-develop-sole-package-in-php81-and-downgrade-to-php72/). But having 2 repositories to work with still feels crappy. Which one should we use? Where do people contribute? Where do we report issues? Everyone needs clarification, and **time is wasted on explaining complexity**. I knew we could do better... we want **one repository**. Today I'll show you how to get there with 39 lines of GitHub Action workflow (including comments). | |
| | | | |
code.dblock.org
|
|
| | | | | You've probably been depending on automated pull requests from Dependabot, but how about making your own pull requests from GitHub actions? This capability can be used for automation that looks for changes, then updates files in your own repository with little to no additional setup needed. | |
| | | | |
blog.martinig.ch
|
|
| | | Informations and opinions about software architecture, developers on call, holacracy, Scrum, continuous testing, product management, saying thank you, tech leadership, customer journey maps, code reviews, code sharing, good bugs, android testing and open source project management. | ||
