{"id":58686,"date":"2026-02-11T06:22:12","date_gmt":"2026-02-11T06:22:12","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=58686"},"modified":"2026-02-11T06:22:12","modified_gmt":"2026-02-11T06:22:12","slug":"gitlab-duo-advanced-practitioner-certified-gitlab-duo-ai-associate-prep-3-days","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/gitlab-duo-advanced-practitioner-certified-gitlab-duo-ai-associate-prep-3-days\/","title":{"rendered":"GitLab Duo Advanced Practitioner + Certified GitLab Duo (AI) Associate Prep (3 Days)"},"content":{"rendered":"\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Duration:<\/strong> 3 days (instructor-led, hands-on)<br><strong>Format:<\/strong> 30% guided instruction &amp; demos, 60% labs, 10% exam-style practice<br><strong>Audience:<\/strong> Developers, DevOps, Security, QA, PMs, Engineering Leads<br><strong>Assumed level:<\/strong> Participants already know GitLab basics (repos, issues, MRs, pipelines)<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">1) Introduction<\/h2>\n\n\n\n<p>GitLab Duo brings AI assistance into everyday GitLab workflows (coding, reviewing, CI\/CD troubleshooting, security understanding, documentation, collaboration). This course makes learners <strong>confident and fast with Duo in real delivery work<\/strong>, while also preparing them for the <strong>Certified GitLab Duo (AI) Associate<\/strong> exam through daily exam-style practice and a final mock.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">2) Course Overview<\/h2>\n\n\n\n<p>This is an end-to-end, workflow-based program using one continuous project scenario. Participants learn to apply GitLab Duo to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>accelerate implementation, refactoring, and understanding of existing code<\/li>\n\n\n\n<li>improve test quality, coverage, and review readiness<\/li>\n\n\n\n<li>interpret findings (security\/quality) and remediate effectively<\/li>\n\n\n\n<li>troubleshoot CI failures and optimize pipelines<\/li>\n\n\n\n<li>improve collaboration artifacts (issues, MRs, docs, handoffs)<\/li>\n\n\n\n<li>use Duo responsibly: governance, data sensitivity, and quality control<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3) Learning Objectives<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">A) GitLab Duo Advanced Practitioner Outcomes<\/h3>\n\n\n\n<p>By the end of Day 3, participants can:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Configure and govern Duo usage<\/strong> at group\/project level (where applicable), and understand who can access what.<\/li>\n\n\n\n<li>Use Duo effectively in <strong>IDE + GitLab UI<\/strong> with strong prompting patterns and \u201cverification-first\u201d habits.<\/li>\n\n\n\n<li>Apply Duo to advanced coding tasks: <strong>generate, refactor, explain, optimize, and document<\/strong> changes.<\/li>\n\n\n\n<li>Use Duo to strengthen <strong>MR quality<\/strong>: better descriptions, reviewer guidance, risk notes, and checklists.<\/li>\n\n\n\n<li>Use Duo to improve <strong>test strategy<\/strong> and create meaningful unit\/integration tests (not just \u201chappy path\u201d).<\/li>\n\n\n\n<li>Use Duo to support <strong>security understanding and remediation<\/strong>, and document fixes clearly.<\/li>\n\n\n\n<li>Use Duo to accelerate <strong>CI\/CD authoring<\/strong> and perform structured <strong>failure analysis<\/strong> from logs.<\/li>\n\n\n\n<li>Measure outcomes and run Duo adoption safely: <strong>quality gates, prompt standards, and ROI signals<\/strong>.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">B) Certification Readiness Outcomes<\/h3>\n\n\n\n<p>Participants will also be able to:<\/p>\n\n\n\n<ol start=\"9\" class=\"wp-block-list\">\n<li>Identify exam-style scenario patterns and avoid common pitfalls (over-trusting AI output, skipping verification).<\/li>\n\n\n\n<li>Explain Duo capabilities, limitations, and responsible usage in clear terms (the kind exams test).<\/li>\n\n\n\n<li>Perform timed question sets with a repeatable strategy.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">4) Participant Profile &amp; Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisites (required)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Basic GitLab workflow knowledge: repository, branches, merge requests, issues<\/li>\n\n\n\n<li>Basic CI\/CD familiarity: pipelines, jobs, logs<\/li>\n\n\n\n<li>General understanding of testing and security basics (what they are, not deep expertise)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended (helpful)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Experience reviewing MRs<\/li>\n\n\n\n<li>Familiarity with one programming language used in your org<\/li>\n\n\n\n<li>Comfort reading pipeline logs and stack traces<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">5) What This Course Is (and Isn\u2019t)<\/h2>\n\n\n\n<p><strong>This course is:<\/strong> practical, hands-on, workflow-based, focused on real productivity and exam readiness.<br><strong>This course isn\u2019t:<\/strong> a Git fundamentals class, or a deep ML\/AI theory course.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">6) Delivery Approach<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Instructor uses <strong>live demos<\/strong> to show \u201cgood vs risky\u201d AI usage patterns<\/li>\n\n\n\n<li>Labs emphasize:\n<ul class=\"wp-block-list\">\n<li>constraint-based prompting<\/li>\n\n\n\n<li>verification (tests, lint, pipeline checks)<\/li>\n\n\n\n<li>MR-ready outputs<\/li>\n\n\n\n<li>security and compliance awareness<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Daily: <strong>exam-style mini quiz + scenario debrief<\/strong><\/li>\n\n\n\n<li>End: <strong>capstone + mock exam workshop<\/strong><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">7) Lab Environment &amp; Materials<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tools needed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>GitLab instance with GitLab Duo enabled (or training environment)<\/li>\n\n\n\n<li>IDE support: VS Code \/ JetBrains (preferred) or Web IDE<\/li>\n\n\n\n<li>A prepared training repository (\u201cAcmePay\u201d) containing:\n<ul class=\"wp-block-list\">\n<li>at least one legacy module<\/li>\n\n\n\n<li>incomplete tests<\/li>\n\n\n\n<li>intentionally flawed pipeline job<\/li>\n\n\n\n<li>intentionally introduced vulnerability or insecure pattern<\/li>\n\n\n\n<li>issue + MR templates (basic)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Working agreements (important)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat AI output as a draft: <strong>verify before merge<\/strong><\/li>\n\n\n\n<li>Do not paste secrets or sensitive data into prompts<\/li>\n\n\n\n<li>Use the <strong>prompt checklist<\/strong> provided in Appendix A<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">8) Core Use-Case Story (Capstone Scenario)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Scenario: \u201cAcmePay\u201d Microservice Modernization<\/strong><\/h3>\n\n\n\n<p>A payment API repository has:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a new feature request with partial legacy code<\/li>\n\n\n\n<li>weak test coverage and missing edge-case tests<\/li>\n\n\n\n<li>insecure configuration or dependency vulnerability<\/li>\n\n\n\n<li>flaky CI pipeline and unclear logs<\/li>\n\n\n\n<li>poor MR descriptions and limited documentation<\/li>\n<\/ul>\n\n\n\n<p>Across 3 days, participants will use GitLab Duo to:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>implement\/refactor safely,<\/li>\n\n\n\n<li>generate and improve tests,<\/li>\n\n\n\n<li>understand and remediate security issues,<\/li>\n\n\n\n<li>troubleshoot CI failures and optimize pipelines,<\/li>\n\n\n\n<li>produce clean MRs and documentation,<\/li>\n\n\n\n<li>summarize impact and adoption signals.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">9) Day-wise Agenda (3 Days)<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Day 1 \u2014 Duo Foundations + Advanced Development &amp; MR Excellence<\/strong><\/h2>\n\n\n\n<p><strong>Theme:<\/strong> \u201cBe productive fast, but safely.\u201d<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Time<\/th><th>Session<\/th><th>What participants achieve<\/th><\/tr><\/thead><tbody><tr><td>09:00\u201309:30<\/td><td>Orientation + course goals<\/td><td>Understand capstone and how exam prep is embedded<\/td><\/tr><tr><td>09:30\u201310:30<\/td><td>Duo capability map + where it fits<\/td><td>Know \u201cwhat to use where\u201d across IDE, MR, pipelines, security<\/td><\/tr><tr><td>10:45\u201311:45<\/td><td>Governance + safe usage practices<\/td><td>Access patterns, data sensitivity, responsible AI behavior<\/td><\/tr><tr><td>11:45\u201312:30<\/td><td>Prompting patterns (advanced)<\/td><td>Convert vague asks into reliable, verifiable instructions<\/td><\/tr><tr><td>13:30\u201315:00<\/td><td>Advanced coding workflows with Duo<\/td><td>Generate\/refactor\/explain with constraints + verification<\/td><\/tr><tr><td>15:15\u201316:30<\/td><td>MR excellence with Duo<\/td><td>Produce MR summaries, risk notes, test plans, review checklists<\/td><\/tr><tr><td>16:30\u201317:30<\/td><td>Exam practice block (Day 1)<\/td><td>15 timed questions + debrief (why each option is right\/wrong)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Day 1 Labs (hands-on)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Environment warm-up<\/strong>: Duo access, IDE connection, repo walkthrough<\/li>\n\n\n\n<li><strong>Feature build with guardrails<\/strong>: implement a new endpoint\/module with constraints:\n<ul class=\"wp-block-list\">\n<li>style rules<\/li>\n\n\n\n<li>error handling<\/li>\n\n\n\n<li>logging<\/li>\n\n\n\n<li>testability requirements<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Legacy code comprehension<\/strong>: ask Duo to explain, then create a refactor plan<\/li>\n\n\n\n<li><strong>Refactor execution<\/strong>: apply refactor + minimal tests<\/li>\n\n\n\n<li><strong>MR packaging<\/strong>: generate:\n<ul class=\"wp-block-list\">\n<li>MR description<\/li>\n\n\n\n<li>change summary<\/li>\n\n\n\n<li>risk notes &amp; rollback hint<\/li>\n\n\n\n<li>reviewer checklist<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Day 1 Deliverables<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>One MR opened with strong description and checklist<\/li>\n\n\n\n<li>Refactor plan notes + implemented improvement<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Day 2 \u2014 Testing &amp; Security: Quality That Scales<\/strong><\/h2>\n\n\n\n<p><strong>Theme:<\/strong> \u201cMake AI raise quality, not just speed.\u201d<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Time<\/th><th>Session<\/th><th>What participants achieve<\/th><\/tr><\/thead><tbody><tr><td>09:00\u201310:15<\/td><td>AI-assisted test strategy<\/td><td>Decide <em>what<\/em> to test, not just generate tests<\/td><\/tr><tr><td>10:30\u201312:00<\/td><td>Test generation + coverage uplift lab<\/td><td>Create meaningful tests (edge cases + negative tests)<\/td><\/tr><tr><td>13:00\u201314:15<\/td><td>Secure coding with Duo<\/td><td>Use AI to explain risks and propose safer patterns<\/td><\/tr><tr><td>14:15\u201315:15<\/td><td>Remediation workflow<\/td><td>Implement fixes + document security decisions clearly<\/td><\/tr><tr><td>15:30\u201316:15<\/td><td>MR review simulation<\/td><td>Use Duo to help structure review comments and verify changes<\/td><\/tr><tr><td>16:15\u201317:30<\/td><td>Exam practice block (Day 2)<\/td><td>15 timed questions + weak-area drills<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Day 2 Labs (hands-on)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Test suite build-out<\/strong> for feature and refactor:\n<ul class=\"wp-block-list\">\n<li>unit tests with edge cases<\/li>\n\n\n\n<li>failure-path tests<\/li>\n\n\n\n<li>simple integration tests if applicable<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Quality uplift<\/strong>:\n<ul class=\"wp-block-list\">\n<li>identify gaps<\/li>\n\n\n\n<li>improve assertions<\/li>\n\n\n\n<li>remove flaky patterns<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Security investigation<\/strong>:\n<ul class=\"wp-block-list\">\n<li>use Duo to explain a vulnerability or insecure code pattern<\/li>\n\n\n\n<li>propose remediation options with tradeoffs<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Remediation + verification<\/strong>:\n<ul class=\"wp-block-list\">\n<li>implement fix<\/li>\n\n\n\n<li>pipeline run<\/li>\n\n\n\n<li>produce security-focused MR notes<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Day 2 Deliverables<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increased test coverage and improved test quality<\/li>\n\n\n\n<li>Security fix documented in MR notes (what, why, how verified)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Day 3 \u2014 CI\/CD Troubleshooting + Collaboration + Full Certification Prep<\/strong><\/h2>\n\n\n\n<p><strong>Theme:<\/strong> \u201cOperate Duo at team scale; finish exam-ready.\u201d<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Time<\/th><th>Session<\/th><th>What participants achieve<\/th><\/tr><\/thead><tbody><tr><td>09:00\u201310:15<\/td><td>AI-assisted CI\/CD authoring<\/td><td>Generate\/optimize pipeline changes safely<\/td><\/tr><tr><td>10:30\u201312:00<\/td><td>Failure analysis &amp; root cause workflows<\/td><td>Use Duo to form hypotheses + verification steps from logs<\/td><\/tr><tr><td>13:00\u201314:00<\/td><td>Duo for collaboration &amp; documentation<\/td><td>Create issue updates, release notes, and handoffs<\/td><\/tr><tr><td>14:00\u201314:45<\/td><td>Measuring impact + adoption standards<\/td><td>Define KPIs and guardrails; create team prompt standards<\/td><\/tr><tr><td>15:00\u201316:15<\/td><td>Capstone execution<\/td><td>End-to-end: build \u2192 test \u2192 secure \u2192 ship with Duo<\/td><\/tr><tr><td>16:15\u201317:30<\/td><td>Mock exam + review workshop<\/td><td>Timed mini-mock + remediation plan for each learner<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Day 3 Labs (hands-on)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Pipeline improvement<\/strong>:\n<ul class=\"wp-block-list\">\n<li>improve job clarity and failure output<\/li>\n\n\n\n<li>reduce flakiness<\/li>\n\n\n\n<li>add missing verification step(s)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>CI failure root cause<\/strong>:\n<ul class=\"wp-block-list\">\n<li>interpret failing logs<\/li>\n\n\n\n<li>ask Duo for likely causes + confidence<\/li>\n\n\n\n<li>validate with targeted checks<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Documentation &amp; comms<\/strong>:\n<ul class=\"wp-block-list\">\n<li>release note draft<\/li>\n\n\n\n<li>issue update summary<\/li>\n\n\n\n<li>QA handoff checklist<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Impact plan<\/strong>:\n<ul class=\"wp-block-list\">\n<li>define 3 KPIs (speed + quality + risk)<\/li>\n\n\n\n<li>create \u201cAI usage guardrails\u201d checklist for your team<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Day 3 Deliverables<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pipeline MR + documented reasoning<\/li>\n\n\n\n<li>Capstone MR with complete evidence (tests, pipeline, notes)<\/li>\n\n\n\n<li>Personal certification action plan (what to review next)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">10) Use Case Library (examples included in exercises)<\/h1>\n\n\n\n<h3 class=\"wp-block-heading\">Development &amp; Refactoring<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Convert a vague feature request into a clean implementation plan + code<\/li>\n\n\n\n<li>Explain legacy logic and propose refactor steps that minimize risk<\/li>\n\n\n\n<li>Generate code with constraints (style, performance, security, testability)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Merge Requests &amp; Review<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Produce high-quality MR descriptions and summaries<\/li>\n\n\n\n<li>Generate reviewer checklists and test plans<\/li>\n\n\n\n<li>Write constructive review comments; identify risky changes<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Testing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Generate meaningful tests from requirements + edge cases<\/li>\n\n\n\n<li>Improve assertions and reliability; avoid brittle tests<\/li>\n\n\n\n<li>Create a test matrix for critical flows<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain vulnerability cause, impact, exploit scenario<\/li>\n\n\n\n<li>Suggest remediation options with pros\/cons<\/li>\n\n\n\n<li>Document security decisions and verification evidence<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">CI\/CD<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Generate or refine <code>.gitlab-ci.yml<\/code> changes responsibly<\/li>\n\n\n\n<li>Troubleshoot failing jobs using structured hypothesis prompts<\/li>\n\n\n\n<li>Improve pipeline observability (logs, artifacts, clarity)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Collaboration &amp; Enablement<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Draft release notes and stakeholder updates<\/li>\n\n\n\n<li>Create reusable prompt templates for team consistency<\/li>\n\n\n\n<li>Define metrics and safe adoption practices<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">11) Assessment &amp; Completion Criteria<\/h1>\n\n\n\n<h3 class=\"wp-block-heading\">Daily checks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>End of each day: 15 exam-style questions (timed) + review<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Capstone rubric (pass\/fail)<\/h3>\n\n\n\n<p>Participants pass if they demonstrate:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Correct use of Duo<\/strong> with clear prompts + constraints<\/li>\n\n\n\n<li><strong>Verification evidence<\/strong> (tests and\/or pipeline results)<\/li>\n\n\n\n<li><strong>MR quality<\/strong>: summary, rationale, risks, test plan, rollback hint<\/li>\n\n\n\n<li><strong>Security handling<\/strong>: explain issue + implement fix or mitigation + document<\/li>\n\n\n\n<li><strong>Operational clarity<\/strong>: pipeline change justified and validated<\/li>\n\n\n\n<li><strong>Impact summary<\/strong>: what improved and how you know<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n","protected":false},"excerpt":{"rendered":"<p>Duration: 3 days (instructor-led, hands-on)Format: 30% guided instruction &amp; demos, 60% labs, 10% exam-style practiceAudience: Developers, DevOps, Security, QA, PMs, Engineering LeadsAssumed level: Participants already know GitLab basics (repos, issues, MRs, pipelines) 1) Introduction GitLab Duo brings AI assistance into everyday GitLab workflows (coding, reviewing, CI\/CD troubleshooting, security understanding, documentation, collaboration). This course makes learners&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-58686","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58686","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=58686"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58686\/revisions"}],"predecessor-version":[{"id":58687,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58686\/revisions\/58687"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=58686"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=58686"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=58686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}