Repository navigation
v1.1.0
GitHub access options, demo notes and build logs.
- GitHub access, three kinds.
setuptakes a fine-grained PAT, a deploy key (pass the path to its private key file; a.pubfile is refused; no passphrase), orpublicfor a public repo. The platform works out which. Source:GITHUB_AUTH(GITHUB_PATstill works) or the hidden prompt, never an option or a conf key. To make a key:ssh-keygen -t ed25519 -N "" -f ~/.ssh/lilypad_<name>, then add the.pubunder the repo's Settings > Deploy keys with write access off. - Notes.
setup --notes "text"orNOTES=in the conf file: up to 1000 characters,\nfor a line break. Leaving them out keeps the stored notes;--notes ""clears them.statusshows them in full,listshows the first 40 characters. build-logs <name> [lines]: the latest build's log, running or finished, for the creator and admins.logsnow shows only the running app. The web client has a Build log tab.- Web client: "GitHub access" field with a Load key file button. The field is required when editing a destroyed demo. A Notes box with a counter; the note preview shows on demo cards and the full notes in the Overview. Public
/helpguide, and setup help in onboarding. - Default size is
tiny. - CI is green again: shellcheck warnings in tests fixed, and the PowerShell conf check now captures the error.
Needs the platform with ADR 022 (build logs) and ADR 023 (GitHub access) plus notes deployed. Pin with LILYPAD_VERSION=v1.1.0.