Activity
Stars and mentions · Last 30 days, Oct 6 – Nov 4
Top repositories
unisoncomputing’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside unisoncomputing’s account where unisoncomputing opened or reviewed pull requests in the past 365 days.
Who noticed unisoncomputing
Everyone who starred or forked unisoncomputing’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories unisoncomputing owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Did unisoncomputing/nimbus work for you at one point? I think the intent is that Nimbus (being written in Unison) is available via Unison Share, but that the README for the now open sourced Nimbus repo links to docs, etc. on GitHub, that originally were more for internal use. I sent an email and got a reply from Paul Chiusano that they're going to take a look and fix those links, which may mean deleting links to e.g., runbooks that might have been more relevant to their internal deployment of Unison Cloud. There's also been some similar questions raised on the Discord earlier today re: broken links in the Nimbus README. You can get the entirety of the Nimbus repo (as I understand it), including the full history, from Unison Share via the Unison Codebase Manager (UCM) with "clone" command.