Should we display the code for the latest release when going to https://github.com/roc-lang/basic-cli instead of the main branch? This would prevent users from trying to use examples that simply won't work with the latest release.
I think that is a good idea. :+1:
Created an issue for this idea here.
Cool, I can have a look later :grinning:
No need, I've submitted a PR to address this and another issue in PR #5718 :)
5 messages were moved from this topic to #ideas > strong module system by Brendan Hansknecht.
Should we display the code for the latest release when going to https://github.com/roc-lang/basic-cli instead of the main branch?
It turns out I can not change the branch that is displayed when going to https://github.com/roc-lang/basic-cli without also making that the default branch. The default branch will be "selected locally" when you clone the repo and is also used automatically as a target for PRs.
So I think we should not make the latest release branch the default branch.
To prevent problems I'll include links to the examples for the latest releases on the main branch's README.
Last updated: Jun 16 2026 at 16:19 UTC