GitHub · GH-700 · BETA
Responsible AI and branch policies
GH-700 · Lesson 2 of 15 · 11:25
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Lesson 2 of the free GH-700 series (domain 1): the six Responsible AI principles of Microsoft and GitHub and how to apply them with Copilot (review and testing, transparency of agent commits and code references, bias, personal data), branch strategies with GitHub flow, and branch policies for people and agents (rulesets, required reviews, status checks, safeguards on pull requests from Copilot cloud agent and automations). With three quick checks and a recap.
Preview the topics
- Contoso wants readers to know which release notes were drafted with AI, and how they were checked. Which principle does that serve?
- Contoso’s team keeps a long-lived branch for every event, and merging them back takes days. What should the team do instead?
- Contoso wants every change to main to have one approval and passing checks, even when an agent opens the pull request. What should the admin set up?