Explore >> Select a destination
|
You are here 
|
roneo.org | ||
| | | | |
emmettnaughton.com
|
|
| | | | | ||
| | | | |
blog.cavelab.dev
|
|
| | | | | When moving my website back from MediaWiki to Hugo - I again started to think about adding comments. I've thought about this before, even tested quite a bit, and written about it. I didn't want to add heavy external resources, or compromise my readers privacy. This blog is static, and I'd like the comments to be static as well. | |
| | | | |
www.zufallsheld.de
|
|
| | | | | Recently, I found myself needing to incorporate a CODEOWNERS-file to multiple repositories within our Github organization. The objective was to automatically reviewers for pull-requests. And codeowners are a perfect tool for this. This way every colleague in our company can join our Github organization and get write-access to the ... | |
| | | | |
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). | ||
