Azure Repos - Scrum Bug

Azure Repos

A collection of 4 posts

The use or uselessness of signed commits

The use or uselessness of signed commits

Each commit you make stores the name and email address you've configured in your git config. But Git doesn't verify whether that's you. You can easily make a commit that uses the email of any famous coder out there in the world, and your Git repo will accept that.

Configuring standard policies for all repositories in Azure Repos

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.

Setting default repository permissions on your Azure DevOps Organization

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.

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

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