The window / Page 16 of 70
This page is one part of The Ishoo manual. The complete manual is a single page, short enough to read in one go: ishoo.app/docs/
Status chips
Ishoo's top chips show main's health (Main healthy, or broken since a commit), whether the store has synced, Catch up when new code is waiting, Agent needed when your copy has its own changes too, and how many landings named no tests.
| Chip | Meaning |
|---|---|
| Main healthy / Main broken since … | Whether a check is known to fail on main. |
| Store synced | Issues and plans match your store's private home. In amber when Ishoo hasn't reached it recently; it keeps trying. |
| Catch up · 3 updates | This copy is missing code from its upstream and has none of its own changes. Click to bring it in. |
| Agent needed | This copy has its own changes and is missing updates. Ask your agent to combine them. |
| 2 untested | Landings that named no tests. The nightly check covers them. |
Ishoo keeps its own records current without asking. Your code only moves when you click Catch up or your agent decides it's safe.