git - Scrum Bug

Use Visual Studio 2022 as merge tool in Tower

Tower recently released a major upgrade of it's already outstanding Git Client. Microsoft shipped Visual Studio 2022 not too long ago either. This is how you integrate the two.

git

Can't push to GitHub "Refusing to allow an OAuth App to create or update workflow without workflow scope"

When any of your commits contain a new or updated GitHub Action, you need to have the `workflow` scope to push these changes. Git Credential Manager for Windows doesn't request this.

azure-repos

Rename your master branch in Azure Repos

Renaming your master branch in Azure Repos could be as simple as a few clicks. But if you have complex policies or permissions in place, it may be a little more work. To rename your master branch you have to create a new branch and then delete the old one:

git

Rename your master branch to something better

I just went through my GitHub repositories to rid them of the master branches. It was a relatively simple process that took me about an hour or 2 for all my repositories. Scott Hanselman explains the base process. It's a simple set of steps to create a new branch with

git

Configure Tower to use the new Windows Terminal

The new Windows Terminal is almost done and the most recent build fixes the one bug that kept me from using it.

git

Launch WSL bash prompt from Tower

When you launch a terminal from Tower, it launches an included MingW bash shell. Now that Windows 10 ships with the Windows Subsystem for Linux it would be nice to use that bash shell instead. My first attempts at launching WSL failed miserably. It looks like Windows Filesystem Redirection causes

Azure DevOps

Configuring standard policies for all repositories in Azure Repos

By default you can only configure policies on specific branches in Azure Repos. If you're using a strict naming pattern for your branches (Release Flow or GitHub Flow), you may want to set a policy for all future Release Branches, or all Feature branches.

git

Setting default repository permissions on your Azure DevOps Organization

There is no UI to set the security at the Organization level. This is fine if you're happy with the default security settings in Azure DevOps, but if you want certain settings to apply to all projects, then it's sometimes useful to set the permissions at the Organization level.

Visual Studio 2017

Use Visual Studio 2017 or 2019 as merge tool in Tower

Updated with Visual Studio 2019 support.I recently started using Tower as my Git client in Windows, it's great in many aspects, but it doesn't ship with any Diff/Merge capabilities. It relies on 3rd party tool to supply that feature. It comes with a long list of supported tools,

git

Configure Visual Studio to use a different Git Credential Manager for Windows

Visual Studio ships with the Git credential Manager for Windows (GCMW) as part of its Team Explorer feature. This nifty little helper allows you to authenticate to Azure Repos among other git providers using your normal username and password and optional 2FA and it will handle the Personal Access Token

Azure DevOps

Connect any version of Visual Studio to Azure DevOps or Azure DevOps Server

Visual Studio has been around for a long time and there are still people developing in Visual Basic 6 or Visual Studio 2008. Even if you're using a more recent IDE, you could need one or more hotfixes and/or service packs.

Team Foundation Server

NDepend 6 offers native integration into TFS 2013

When Patrick Smacchia contacted me a couple of weeks back to look at his new TFS support for NDepend I was very excited. We've integrated NDepend through commandline calls with numerous clients and though that works, it's not very easy to get trend analysis or act upon the findings in

TFS 2013

Configure Git for Visual Studio to use a proxy server

Unlike most features of Visual Studio, the Git tools do not (always) automatically pick up the Widows proxy settings, being dependent on a number of open source libraries which don't seem to be benefiting from the same Windows Proxy Auto-Detection. This is a shame, really, but it doesn't make it

XAML Build

Building a .NET application using the GitUpgradeTemplate.xaml

Today I received a request which I first found strange. A team that migrated to Git, but still wanted to use their TFS 2008 era TFSBuild.proj. After seeing the investment made in that build file, I understood :). So we though to simply use the GitUpgradeTemplate.xaml which is provided

Azure DevOps

Codelens features and Visual Studio versions [Updated for 2013.3ctp1]

Update: Visual Studio 2013.3 CTP 1 Adds support for Git repositories! If you're as happy with the new CodeLens features in Visual Studio 2013 ultimate as I am, you've probably found out that some of the features rely on server side features. This means that some Code Lenses only

Azure DevOps

Use Git commandline directly from Visual Studio

Update: Instead of using the Package Management Console, you can now use The Whack Whack Console, ConEmu Integration or BuiltinCmd for a better interactive console. These can be combined with PoshGit as well. Not many people seem to know this, but the Visual Studio Package manager is nothing more than

Azure DevOps

Microsoft provides full Git support for Visual Studio 2012 and Team Foundation Service

Today Microsoft publicly introduced the first Community Preview version of the Git tools for Visual Studio and the Team Foundation Service at the ALM Summit. Microsoft is fully committed to supporting this open distributed version control platform going forward. This was one of the top requests on Uservoice. It's pretty

Team Foundation Server

Why I like TFS :)

As a response to Joe Ferner's post on why he dislikes TFS. I'll first touch upon the items brought forward by Joe. Some of them are just true, and I won't put too much effort in those, but some I just don't agree with. Joe's complaints CodePlex -- First there