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
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...
Building a CI pipeline for Containerized Asp.NET Core 3.1 using ACR Registry
This is continuation of a series of posts on using Docker and containerization with .Net Core. If you are new to this series its recommend to look at Getting started with Docker and Containers In this post will show how to setup a pipeline that continuously builds a repository that contains a Docker file. Every time you change your code and commit, the image is pushed to ACR Registry. Pre requisites 1. Github account 2. Azure DevOps Organisation if you don’t have one, you can create for free 3. Ensure you’re administrator of the Azure DevOps project 4. Azure Container Registry – more details can be found here 5. Azure Project to be created in Azure DevOps 6. Service Principal created in Azure – Creation process can be found here Get the co...
Building a CI pipeline for Containerized Asp.NET Core 3.1 using Docker Registry
This is continuation of a series of posts on using Docker and containerization with .Net Core. If you are new to this series its recommend to look at Getting started with Docker and Containers In this post will show how to setup a pipeline that continuously builds a repository that contains a Docker file. Every time you change your code, the image is pushed to Docker Hub. Pre requisites 1. Github account 2. Azure DevOps Organisation if you don’t have one, you can create for free 3. Ensure you’re administrator of the Azure DevOps project 4. Docker hub repository – more details can be found here 5. Azure Project to be created in Azure DevOps Get the code from GitHub https://tinyurl.com/ydtggef6 Create the Pipeline 1. Sign in to your Azure DevOps Organisation and navigate to your project 2. ...
Setting up Azure Service Connection in Azure DevOps
You can specify your Azure subscription directly in the release pipeline task, or you can use an organiz ational account or a Service Principal and configure Service connection in Azure DevOps. In this post will see how Service Principal can be created. Tools which can be used to create Service Principal in Azure: Using Azure PowerShell Using Azure Portal Using Azure CLI 2.0 Portal Irrespective of the tool choice commands remain same. There are two types of authentication available for service principals: Password-based authentication, and certificate-based authentication.This post we will be looking demonstrating Password-based authentication. Steps 1. Log into Azure by running the below command. When prompted, open the browser and login with Microsoft credentials. az login 2. Create a Service Principal by running the following command. The output displayed ...