The art of simplicity

Enhance your AI programming skills and take your abilities to the next level! Starting this week, from February 4th to 13th, Microsoft hosts a series of four live classes designed to teach you tips and best practices for using GitHub Copilot. So if you really want to get the most out of your Github Copilot, don’t hesitate to register .   Here is the agenda for the English sessions: February 4, 2025: Prompt Engineering with GitHub Copilot February 6, 2025: Building an AI Web Application with Python and Flask February 11, 2025: Productivity with GitHub Copilot: Docs and Unit Tests February 13, 2025: Collaboration and Deploy with GitHub Copilot Hope to see you all there! More information GitHub Copilot Global Bootcamp | Microsoft Community Hub

Last week a colleague complained to me that he had to wait for an available build agent on our Azure DevOps build server. The reason that all build agents were busy was because I was doing a lot of changes to the documentation(also stored in an Azure DevOps Git repository) causing a lot of builds to be triggered resulting in long wait queues. As only changing the markdown files in the wiki doesn’t need a build to be created, he asked me to configure the build trigger to ignore documentation changes. Let me show you how to configure this… Classic Pipelines To configure this for the ‘classic’ pipelines in Azure DevOps, you need to go to the Triggers tab for your pipeline. There you’ll find a Path filters section on the right where you can specify specific paths to include or exclude. In our example, we want to exclude everything inside the ‘SOFACore/Docs’ folder:   YAML Pipelines If you are using a YAML pipeline, you need to edit the trigger section and add a path e...