📊 We use cookies & analytics to improve your experience. Learn more
Latest

GitHub Copilot Mastery — AI Pair Programming That Ships Module 3 · Lesson 11 of 15

0% Exit to course

Module 3 · Files, tools and your own data Lesson 11 of 15

Automate one boring task with GitHub Copilot

Learning objective

Automation is not about building a system. It is about doing one repetitive job the same way every time, in less time than last time, and being able to do it again next month.

The concept

Pick the task by how often it happens, not by how impressive it would be. A weekly report you can half-generate beats a clever pipeline you build once and never open again.

Generating the test file for every new function, or drafting the pull-request description from the diff.. Whatever you choose, write the steps back out in plain English afterwards — "Step 1, open the sheet, Step 2, paste the names —" because the written steps are what you follow when the tool changes next quarter.

And keep a copy of the prompt next to the task. A prompt that lives only in your chat history is a prompt you will rewrite from scratch in March.

Worked example

A pull-request template that starts with the summary the assistant generated, which you then correct, saves the five minutes you spend staring at a blank box.

Your practice task

Name the task you repeat most often that involves typing, then write the prompt for it and run it three weeks in a row from the same saved place. Three runs is the point at which you know whether it is genuinely automated.

Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.

Key takeaway

Pick the task by how often it happens, not by how impressive it would be.

Create free account or sign in

Almost there

15 lessons left of 15

Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.