Explore >> Select a destination
|
You are here 
|
gribnau.dev | ||
| | | | |
duerrenberger.dev
|
|
| | | | | In September there seems to have been some spam on GitHub leaving behind Ghost Notifications, fortunately there's a way to remove these via GitHub's API | |
| | | | |
yos.io
|
|
| | | | | There isn't one. But here are a few options. | |
| | | | |
kinoshita.eti.br
|
|
| | | | | Some months ago I noticed that even after I marked all my GitHub notifications as read, the unread icon displayed at the right top corner was still showing as if I had unread notifications. GitHub Notifications icon always-on mode I tried changing the filters, waiting for a new notification to appear so that I could mark it as read, all hoping that icon would then change. But no matter what I tried in the GitHub UI, the icon was still there. | |
| | | | |
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). | ||
