GitHub Copilot Customization Explained for Beginners: Instructions, Prompt Files, Skills, Agents, and Hooks Introduction If you've recently started using GitHub Copilot, you've probably come across terms like Instructions , Prompt Files , Skills , Agents , and Hooks . At first glance, they all seem to do the same thing—they tell Copilot what to do. So why does GitHub have five different customization features? The answer is simple: each feature solves a different problem. Think of GitHub Copilot as a new developer joining your team. On their first day, you don't just hand them code. You explain your coding standards, give them reusable templates, teach them specialized knowledge, assign them a role, and automate repetitive tasks. That's exactly how GitHub Copilot customization works. In this article, you'll learn what each feature does, when to use it, and how they all work together. By the end, you'll know which feature to start with and which ones can wait un...
Posts
Swagger UI for Azure Function v2 & v3 APIs
In this blog post, we will see how to setup Swagger UI for Azure Function APIs in v2 and v3. Now you might be wondering why Swagger? Swagger is a language-agnostic specification for describing REST APIs, it also referred to as OpenAPI. Swagger UI offers a web-based UI that provides information about your REST APIs service. Prerequisites HTTP trigger Azure function provisioned or created in C# Azure DI enabled on Azure Function, for more details refer here with relevant package version installed based on Azure Function version. Integrating Swagger UI into our Applications 1. Install the appropriate package based on the Azure Function version which you are dealing with from the below table. Unfortunately, it's not a single package for both versions due to Azure function v3 because v3 makes use of ASP.NET Core 3.1 which introduces a new serializer System.Text.Json (STJ) out-of-the-box. Azure Function Version Nuget package v2 ...
Azure DevOps Tips: How to set default branch name for new repos?
Recently Azure DevOps came up with a new feature of setting the default branch name for new code repos. Based on my experience, most of the projects or organizations use the master branch to refer to the official release history (which is deployed into production), and the develop branch serves as the integration branch for features. Azure DevOps Git Repositories by default the branch name is set to master, and whenever we create new repositories, it takes that as default. In a nutshell, if organizations who are following Gitflow Workflow having the default branch as a master doesn't work well, which means as part of creating a new repository need to follow a two-step process where first they need to create a repo and then navigate to branches of the project à select the branch of your preference and click on the three-dot icon to set as the default branch. Set Default Branch - old way How to set the Default branch name for new repos in Azure DevOps? With the ne...