GitHub Actions
An event starts a workflow of jobs and steps
An event starts a workflow. Its jobs run on runners, step by step.
GitHub Actions is automation built into every repository. It begins with an event. Here, someone pushes to main. The event starts a workflow. A workflow is a file in the repository that describes what to do. The workflow contains jobs, and each job runs on a runner: a fresh machine that GitHub provides. A job is a list of steps. Check out the code, set up the tools, run the tests. A step is either a command, or a ready-made action.
GitHub Actions · Going deeper
The words of GitHub Actions
Workflow, event, job, step, action, runner.
GitHub Copilot
From finishing a line to finishing a task
Suggestions, chat, agent mode and the cloud agent: rising autonomy.
GitHub Copilot is an A I assistant, and it works at four levels. Suggestions complete your code as you type. Chat answers questions, explains code and drafts things for you. Agent mode goes further. In your editor, it plans a task, edits several files, runs commands and fixes what fails. And the cloud agent works on GitHub itself. You assign it an issue, and it comes back with a pull request. The higher the step, the more Copilot does, and the more you review.
GitHub Copilot · Going deeper
Copilot capabilities
Multi-model support, code review, and a person always decides.
Check yourself
Which Copilot capability is this?
Copilot plans
Business and Enterprise add control, not just capacity
Individual plans serve one person. Business and Enterprise add seats and policies.
The exam asks how the Copilot plans differ. Individual plans are for one person, who pays for themselves. They give suggestions, chat and agents. Nobody else controls them. Copilot Business is for an organization. It adds central management: who has a seat, and policies for everyone, such as which features and models are allowed. Copilot Enterprise has all of that, with the most capacity and priority access. It requires GitHub Enterprise Cloud.
Copilot plans · Going deeper
The plans and the policies
Free, Pro, Business, Enterprise, and content exclusion.
Editors in the browser
github.dev edits. A codespace also builds and runs
github.dev is a free, instant editor. A codespace is a full machine with a terminal.
GitHub offers two editors that run in the browser, and they are easy to confuse. G I T hub dot dev opens when you press the full stop key in any repository. It is instant and free. You can edit files, commit and open a pull request. But it has no terminal, and cannot run anything. A codespace is a complete virtual machine in the cloud, with your repository already on it. It has a terminal, and it can build, run and debug your code.
Editors in the browser · Going deeper
About Codespaces
Machine types, billing, idle timeout and prebuilds.
Check yourself
What does this file set up?
Dev containers
One file gives every codespace the same setup
A devcontainer.json file defines the image, tools, ports and extensions.
How does a codespace know what to install? From a file in the repository: dev container dot J son. This one names a base image with Node, a port to forward, a command to run after creation, and an editor extension. Whenever anyone creates a codespace for this repository, they get that environment. Node is installed. The port is forwarded to their browser, and the dependencies and the extension are ready. Nothing to set up by hand.
Dev containers · Going deeper
Clue words for Actions, Copilot and Codespaces
Workflow, runner, agent mode, Codespaces and github.dev.
Check yourself
Which tool fits best?
Lesson complete
You finished “Actions, Copilot and Codespaces”
Answer the questions along the way to see your score here.