3 docs tagged with "app-works"

Use when a Task asks you to prepare a pull request to the original open-source project behind a fork — "Prepare upstream pull request: …" or "Address review on upstream pull request #…". Covers porting exactly one already-merged change onto a clean branch from the project's default branch, following the project's contribution guide and pull request template, running its documented checks, disclosing AI assistance, and stopping when the project requires a signature or does not accept AI-assisted contributions.

Use when a Task asks you to change an App Work — a running open-source application the owner forked, copied or linked into Ever Works — for example "add an SMS reminder", "fix the failed deployment of 3f9c2ab", or a Goal iteration or Mission Task filed on that App Work. Covers planning within the app's size guidance, respecting its protected paths and human-merge paths, running its declared checks, and writing a reviewable pull request against the branch the app deploys from.

Work out how to build and run an arbitrary repository as an Ever Works App Work, and write its App spec (.works/works.yml, kind app) plus an overlay Dockerfile only when unavoidable. Use when a Task asks you to provision, re-provision or fix the App spec of a repository — never to change the application's own code.