Authenticating to GitHub using Git for Windows and a Personal Access Token fails

While following this guide to migrate to using multiple GitHub HTTPS accounts on Windows from a single user account I have used for years, I had to remove my existing credentials from Windows Credential Manager. When re-authenticating via the prompted login window: to existing repos on using an existing Personal Access Token or authenticating to a new repo using a different account on an instance of GitHub Enterprise using a new Personal Access Token, I would receive a combination of the following errors:

Changes to a PowerShell Module Manifest not viewable in Git

When you make a change to a PowerShell Module Manifest and go to commit those changes in Git, I have observed for some time that it was not possible to see the actual changes in the file because Git was showing it as a binary file. I finally found out why this happens…… Take the following example. I’ve created a module manifest for a module Test with New-ModuleManifest: Now I make a change to the manifest, say up the version to 1.

Can't Clone Git Respository in SourceTree: Failed to connect....No error

While attempting to clone a Git based repository in Stash via the SourceTree client, I received the following error: fatal: unable to access ‘http://[email protected]:443/repo.git/': Failed connect to company.local:443; No error No error obviously doesn’t give many clues, however this post suggested something to do with proxy settings. My web browsers were configured to use an internal web proxy via an automatic configuration script and I could successfully navigate to the repository via a web browser.

Using Git, Stash and Dropbox to Manage Your Own Code

Sometimes I’m asked how I manage my own (PowerShell) code, in terms of version control, backups, portability etc. In this presentation I demonstrated how my PowerShell code is typically broken down into functions and then placed into modules. This allows me to make very generic code for granular tasks, typically either to plug a gap missing from the out-of-the-box cmdlets or maybe stringing a few of them together. As a consultant this enables me to build up a toolkit of functions for particular scenarios gained over various different experiences and use them in a modular fashion where needed for each particular project.