First Team Release

The situation

Real internal test accounts have been polluting the monthly creator reports for months — anyone whose handle starts with 'test-' shows up in the numbers a partner sees. There's a small fix for it, and Maya has decided it's the one you take through Code Nexus's full release workflow, end to end, with all four mentors watching.

What you'll learn

• GitHub Foundations consolidation: the full issue -> branch -> review -> merge -> verify -> release flow, a release checklist and its residual risk, and rejecting a confident bad fix. Spirals Linux verification, Python, and the API/SQL bridge.
• A programme practice checkpoint across GitHub Foundations topic areas. Its item count and weights are programme design choices, not a validated exam predictor or guarantee of current provider coverage.

Who you work with

• 

  Maya Chen

  Senior AI Engineer · Your mentor

• 

  Kabelo Mokoena

  Platform and DevOps Engineer

• 

  Lydia Roe

  Security Engineer

• 

  Amara Okafor

  ML and Data Engineer

• 

  Leo Martins

  Product Manager

• 8-BIT

  Code Nexus Internal AI Assistant

Scenes

1. 1.The one you ship
2. 2.Read the checklist
3. 3.The reviewed patch
4. 4.Verify it on the box
5. 5.The report that came back empty
6. 6.GitHub Foundations practice checkpoint

What you leave with

You took issue #47 from the ticket to production through Code Nexus's full workflow — reviewed patch, protected merge, verified on the Linux box — named the residual risk before it happened, and when it did, rejected 8-BIT's fix that would have reintroduced the original bug in favour of filtering on the explicit is_test flag.