Note 🔗This is part of a series of posts discussing Dependency Injection. It is aimed at explaining dependency injection in a way that non-technical users can understand, and will purposely gloss over some of the more advanced topics. Additional content in this series: Fuel Injection? More Like Dependency Injection I’ve been learning about dependency injection in .NET. Or, more accurately: I’ve been realizing that I already knew about dependency injection in .

For a while at Chocolatey, we have had a Slack channel for things we learned. For almost as long I have been meaning to add a post about the things I learned to my blog. Recently, Julia Evans shared about her creation of a small “TIL” section on her site. With that in mind, I have created a “TIL” tag on my blog, as well as redirecting https://coryknox.dev/til to the listing page for the tag.

I learned this on CSharpFritz’s stream: git config --global --add --bool push.autoSetupRemote true. This allows you to be able to just do git push and it’ll automatically setup a remote tracking branch on your default remote.

Today I learned from Scott Chacon about the --force-if-includes on git push. When used alongside --force-with-lease will negate the troubles potentially caused by applications that periodically git fetch for you. Basically it will prevent you from pushing if you’re pushing to a remote that has a commit that is not a common ancestor of what you’re pushing I think… If my testing is correct, then it’ll act like --force-with-lease when the remote has not been fetched down, but in the scenario where it has actually been fetched down.

I’ve learned that you can do git stash -u to stash untracked files as well as tracked files… But nothing will show you those files in the stash by default… Instead, if you do git add <untracked files> and then git stash, they are magically tracked files even if they’re not actually committed to the repository.

VS Code is pretty amazing. Having the ability to edit virtually all of your files, and launch debugging sessions of them. But what if you have a codebase that has a .vscode/launch.json file and want to debug a PowerShell script? Unfortunately, by default, F5 will only debug PowerShell if there are no debugger configurations. This means that pressing F5 will attempt to run the configured debugger for your workspace regardless of if you’re in a PowerShell file.