Discussion

How much time do you waste trying to run a new GitHub repo?

I'm building a tool where you paste a GitHub URL, and it auto-detects the stack (Node, Python, Go, etc.), spins up a sandbox, and runs it immediately. No config, no git clone, no dependency hell.

My use case is auditing open-source tools or testing libraries quickly without polluting my local machine or dealing with version conflicts.

My question to the community:

Do you use existing tools (Codespaces, Gitpod) for this? I find them too "heavy" for just checking if a repo works.

Is the friction of npm install / pip install high enough that you'd use a "one-click run" service?

Or do you prefer reading the code statically and never running it?

4 points prabhavsanga 10 months ago 3 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton