learnings on Cory Knox

New TIL tag and posts

Tue, 12 Nov 2024 00:00:00 +0000

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.

Also at Julia’s encouragement, I have created a PowerShell script that will create a new page for me and open the file in vscode.

Automatically setup remote tracking branch

Wed, 23 Oct 2024 00:00:00 +0000

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.

Prevent force pushing even when remote is fetched automatically

Wed, 23 Oct 2024 00:00:00 +0000

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. (Source: https://git-scm.com/docs/git-push#Documentation/git-push.txt---no-force-if-includes)

Stash untracked changes in a way that git stash reports them

Wed, 23 Oct 2024 00:00:00 +0000

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.

Run PowerShell no matter what

Fri, 23 Feb 2024 00:00:00 +0000

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.

Fear not! Although by default you’re not able to run PowerShell code with F5 when a debugger configuration exists, you are able to tell VS Code you want to do this!

Doing it through the GUI 🔗

If you’d like to add this through the VS Code GUI, you can follow these steps:

Open the Keyboard Shortcuts UI (Ctrl + K, Ctrl + S by default, or search for Preferences: Keyboard Shortcuts with the Command Palette), then search for PowerShell: Run.
Locate and double click the entry for PowerShell: Run
Press F5 followed by Enter
Right click the entry and choose Change When Expression
Enter the following for the expression: editorTextFocus && debugState == 'inactive' && editorLangId == 'powershell'
Bask in the glory that is pressing F5 in a PowerShell script and always having it do what you expect it to do.

Doing it through the `keybindings.json` file 🔗

If you’d prefer to just copy/paste something into the settings files, you can add the below to your keybindings.json file:

[
    {
        "key": "f5",
        "command": "PowerShell.Debug.Start",
        "when": "editorTextFocus && debugState == 'inactive' && editorLangId == 'powershell'"
    }
]

You can locate your keybindings.json file through the Command Palette Preferences: Open Keyboard Shortcuts (JSON).

learnings on Cory Knox

New TIL tag and posts

Automatically setup remote tracking branch

Prevent force pushing even when remote is fetched automatically

Stash untracked changes in a way that git stash reports them

Run PowerShell no matter what

Doing it through the GUI 🔗

Doing it through the keybindings.json file 🔗

Doing it through the `keybindings.json` file 🔗