You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo "this is not valid javascript %%%" >> Solutions/JavaScript/The-Clockwork-Town-of-Tempora/The-Clockwork-Town-of-Tempora.js
1543
+
echo "this is not valid javascript %%%" >> Solutions/JavaScript/The-Clockwork-Town-of-Tempora.js
1544
+
```
1545
+
1546
+
**PowerShell (Windows):**
1547
+
1548
+
```powershell
1549
+
Add-Content -Path .\Solutions\JavaScript\The-Clockwork-Town-of-Tempora.js -Value "this is not valid javascript %%%"
1543
1550
```
1544
1551
1545
1552
Commit, push, and create a PR:
@@ -1563,9 +1570,40 @@ gh pr create --title "Test: Trigger CI Doctor" --body "Intentionally breaking a
1563
1570
- Specific recommended fixes with file paths
1564
1571
- Prevention tips
1565
1572
1566
-
**Step 8: Clean up**
1573
+
> **💡 Tip: Automatic triggering on CI failure**
1574
+
>
1575
+
> The workflow we created uses `label_command` — you manually add the `ci-doctor` label to trigger it. If you want the CI Doctor to run **automatically** whenever CI fails, replace the `on:` trigger in `ci-doctor.md` with:
1576
+
>
1577
+
> ```yaml
1578
+
> on:
1579
+
> label_command:
1580
+
> name: ci-doctor
1581
+
> events: [pull_request]
1582
+
> workflow_run:
1583
+
> workflows: ["CI"]
1584
+
> types: [completed]
1585
+
> conclusions: [failure]
1586
+
> ```
1587
+
>
1588
+
> This keeps the label-based on-demand trigger **and** adds automatic activation whenever the CI workflow completes with a failure. After changing the trigger, recompile with `gh aw compile ci-doctor`, commit, and push.
1589
+
1590
+
**Step 8: Clean up or fix**
1591
+
1592
+
Once you've reviewed the CI Doctor's diagnosis, you have two options:
1593
+
1594
+
**Option A: Ask Copilot to fix it**
1595
+
1596
+
Instead of fixing the issue manually, you can comment on the PR:
1597
+
1598
+
```
1599
+
@copilot fix the issue
1600
+
```
1601
+
1602
+
Copilot will pick up the CI Doctor's diagnostic comment and use it as context to create a fix commit directly on the PR branch. This isn't the CI Doctor workflow — it's GitHub Copilot's built-in PR capability, but it leverages the diagnosis the CI Doctor already posted.
1603
+
1604
+
**Option B: Clean up the test branch**
1567
1605
1568
-
Once you've seen the CI Doctor in action:
1606
+
If you just want to discard the intentional breakage:
0 commit comments