Explore >> Select a destination
|
You are here 
|
coryknox.dev | ||
| | | | |
www.michaelcrump.net
|
|
| | | | | Learn how to deploy Azure Functions with Visual Studio Code | |
| | | | |
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 | |
| | | | |
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. | |
| | | | |
chambers.io
|
|
| | | So far this week we've talked about what Git is and how to use it. If you're anything like me, you want to know how things work under the hood. When you first learn Git it can seem like magic...but it also seems like something that can easily break. Or something that works by pure demonic byte voodoo. One of the best things Git does is allow you to write code with confidence - fear not about breaking things or losing files. They're always recoverable. To feel confident, it helps to know how things work. | ||
