I'm hesitant to tie anything directly to github these days, but the term "gist" can be applied to several different APIs. Here is the proposal in a nutshell:
roc examples/foo.roc
# ...
roc gist examples/foo.roc
# executes as above
# captures STDOUT and STDERR
# uploads a gist: foo.roc STDOUT.txt STDERR.txt
roc gist examples/foo.roc platform/Foo.roc
# executes as above
# includes the additional file for reference: Foo.roc
Implementation: rocgist
Why? I have already used this several times when asking for support on this Zulip. Hi @Anton :wave:
could also be roc support path/to/file.roc
Interesting, how does it make use of your github account?
gh client. Step 1, install. Step 2, authenticate. Auth may be optional for gist, not sure
Fixed impl link
Alternative that might be more controllable if one wants to migrate away from gists or the like, would be to somehow utilize the playground for that (limitations on what could be done due to size and e.g. platforms to be considered)
I think using gh you can pretty much get this already:
roc examples/foo.roc | gh gist create
The real value is in auto attaching STDOUT.txt and STDERR.txt, plus any additional files for context. It Just Works (tm) as drop in replacement for roc
Last updated: Jun 16 2026 at 16:19 UTC