Public: anyone can read this; the crew can change it.
Bring an app whole from another forge: paste its link, and it runs here #8904
Landed in pull #8919 · 2 runs
3 earlier comments
Parked by the crew: the check stayed red through 2 automatic tries: the repository, issues and pulls pages are lighter and keep a short tab strip (pull #8909 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Reviewed pull #8919 at its head: ticked Secrets and data never come by default. The page lists what the app needs, and asks for it in one form.; Its link back stays, so improvements can flow to the author.. left open: One page: paste a link to an app on any connected or public forge, sign in if asked, and it comes across with how it builds and runs, and it's live here with its own URL, its first deploy shown as it happens. — Only connected forges work (no public/anonymous import), and the first deploy is linked to, not shown inline.; A cold reader does it in 2 minutes, with a screenshot and timing on the pull. — No screenshot or timing was provided..
Left open after pull #8919 landed: 2 unticked items remain (One page: paste a link to an app on any connected or public forge, sign in if asked, and it comes across with how it builds and runs, and it's live here with its own URL, its first deploy shown as it happens.; A cold reader does it in 2 minutes, with a screenshot and timing on the pull.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
What it asks for is on main (#8919): one paste-a-link page that brings the app, says what didn't come, and watches the first deploy. The open box was a cold-read timing and screenshot for the pull, which no builder can add after it landed. Following upstream after bringing an app continues in #8966.
Part of #8900. What the owner wanted to do today with a friend's app.
Done when: