Skip to content

docs: restore the wrong-service-name warning, corrected (86c990cfh) #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Babissimo merged 1 commit into from
Aug 20, 2026
Merged

docs: restore the wrong-service-name warning, corrected (86c990cfh) #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions ONBOARDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,6 +237,10 @@ branch, open a PR, get it green, then merge.
branch got no tests, no lint and no build while the lone green automated-review
tick made the page read as passing. Stacked PRs opened since run the full matrix,
but an older branch keeps the old workflow until it is rebased.
- **The compose service is `server`, not `tower-finder`.** Naming a service that
does not exist fails with `no such service` on *stderr*, so a `grep` over the output
matches nothing and reads as a clean "no errors in the logs". Run `docker compose ps
--services` first and trust it over a remembered name.
- **A new per-environment key needs an `env-parity` entry** or CI fails.

## Where to go next
Expand Down
Loading