Git is a powerful tool with lots of options to simplify how you work. Today we explore how to specify files and folders to automatically ignore for all local repositories, as well as how to configure Git tracking without a local .gitignore.

If you’re moving to GitHub from Azure DevOps, you may miss the presence of variable groups for centralizing settings. At first glance, this feature appears to be missing from GitHub. It turns out that it just requires a bit of creativity to make this functionality available.

Having templates for your company or your personal projects can improve your development life and enable collaboration. In order to take full advantage of this, we need to make the packages we’ve created available to the rest of our team. To do this, we need a package management solution, such as GitHub Packages.

Part of DevOps is supporting the people and processes with the right tools. There is one tool that is particularly powerful for organizations — reusable templates that make it easy to share best practices for new files and projects. In today’s post, we’ll explore creating a template that uses dotnet new to package and distribute a file.

It’s a best practice to use private registries such as Azure Container Registry with container solutions on Azure. There’s very little guidance if you’re considering using a different registry to store your images. In this post, we’re explore how to use other private registries, such as the GitHub packages Container Registry.