Explore >> Select a destination
|
You are here 
|
sitr.us | ||
| | | | |
huey.xyz
|
|
| | | | | Triggering a GitHub action from a git push from another GitHub action. This site is a static site with a deployment pipeline that comprises various daisy-chained GitHub actions. For example, there is a GitHub action that checks my BookWyrm orreadi.com profile periodically, and updates a JSON file in the GitHub repository for this site if there are changes to the books... | |
| | | | |
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). | |
| | | | |
lea.codes
|
|
| | | Sprinkle your JavaScript codebase with type annotations in JSDoc, run checks against it and auto-generate documentation. | ||
