Repairing a CI Script Injection is a practical course for beginners who can enter terminal commands. A preview build accidentally treats a contributor's title as executable shell text. You will preserve useful metadata handling while removing that ability.
One Guided Lab introduces the business workflow, traces real Bash execution, and teaches a small JSON and shell repair. One Challenge transfers the same technique to multiline release notes. The complete course takes about 85 minutes.
What You Will Learn
- Trace event data into generated shell source and recognize the substitution boundary.
- Pass metadata through environment variables and expand it safely with quotes.
- Preserve punctuation, literal shell-looking text, and final line breaks.
- Test real artifacts and release-channel integrity in disposable workspaces.
Who This Course Is For
This course suits beginning developers, security learners, and people exploring CI. Basic terminal familiarity is required; Git and CI experience are not. The Guided Lab teaches the JSON, Bash syntax, and file-writing method used in the Challenge.
LabEx provides a prepared Linux terminal and a local runner with a Topology page. You edit two short files. Builds use real Bash inside isolated containers; there are no hosted accounts, deployment credentials, or real releases.
Frequently Asked Questions
Do I need a GitHub account?
No. Synthetic events and a documented small local job format let you study the input-to-shell mechanism without a hosted CI service.
Will I write code?
You make a small JSON environment mapping and a short Bash script edit. Each required syntax feature is explained before use.
What counts as completion?
The unchanged submitted job must produce exact metadata artifacts and keep the preview channel for normal and hostile fixtures. Tests use scratch workspaces; no report or copied log is required.
