Cert EspressoLearn. Practise. Find your flow.

A LITTLE FOCUS.
A BIG NEXT STEP.

Your pace. Your space.
Microsoft · AZ-401 · BETA

GitHub Agentic Workflows and pipeline health

AZ-401 · Lesson 10 of 18 · 1:22:03

YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗

In this lesson

Lesson 10 of the free AZ-401 series (domain 3): GitHub Agentic Workflows (public preview: Markdown instructions compiled with gh aw, engines, safe outputs and other guardrails), monitoring pipeline health (failure rate, duration, flaky tests), optimizing pipelines, and retention of runs, artifacts, caches, and packages. With three quick checks and a recap.

Preview the topics
  • An agentic workflow should comment on new issues with a suggested label, but never push code. What limits it to that?
  • A test fails about once in ten runs on main, with no code change, and it blocks unrelated pull requests. What should the team do first?
  • Contoso must keep the artifacts of every production release for a year, but daily test builds fill the storage. What should the team set up?