/explore
|
You are here 
|
sitr.us | ||
| | | | |
engineering.hashnode.com
Monitor AWS CDK changes with CDK diffs in GitHub PRs for streamlined development and robust cloud management. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
eran.sandler.co.il
It's time to move my blog to version 3. This time we are going back in time and into the future at the same time. Before we begin, here is a little history of my blog: Version 1 - Blogger Version 1 ran on Blogger - which was essentially a static site generation platform. It gave you an editor, you would write your posts and then it would generate your complete site in HTML and even allowed you to publish it on your own server by uploading the result via FTP. |
|
| | | |||
