silo-evidence

Publishes Silo QA evidence (screenshots, recordings, logs, and notes) to the private evidence site that Silo pull requests link to. Only you and the Silo team can open what you publish.

npm install -g @silo-server/evidence
silo-evidence login                      # approve this computer in the browser, once
silo-evidence new evidence/my-change     # writes a notes.md to fill in
silo-evidence publish evidence/my-change # prints the link for your pull request

Notes

notes.md becomes the page. Its front matter needs a title; summary, pr, issue, validation, target, and build are optional. Images, recordings, and text files the body links to are uploaded; nothing else in the folder is. Images captioned Before: … and After: … pair up into a comparison.

---
title: Search finds people by director
summary: Searching a director's name now lists them under People.
pr: 2016
---

## Steps

1. Search for "nolan" on the web client.

![Before: no people](before.png)
![After: people first](after.png)

Search response, trimmed: [search.json](search.json)

Text files are checked for things that look like secrets before anything is uploaded.

Commands

| Command | Does | | --- | --- | | login | Signs this computer in through the browser and saves an API key | | whoami | Shows who you publish as | | new <dir> | Writes a notes.md with the standard sections | | publish <dir> | Publishes the folder; --note says what changed, --dry-run only checks | | delete <repo>/<topic>[/<version>] | Deletes evidence you published | | logout | Removes the saved key |

SILO_EVIDENCE_KEY overrides the saved key, for example in CI; create one under API keys on the site. Exit codes: 0 done, 1 usage, 2 folder problem, 3 possible secret, 4 not signed in or key refused, 5 upload failed, 6 not allowed.