albertchae

Thanks @exu3 I think that's actually what he said and I misremembered. I'll edit the issue to match your details

@simi thanks for all the reviews and comments so far. Was there anything else you wanted me to address for this PR?

Discussed in marketing meeting: @garbas suggested using only the icon instead of handle, and go back to inlining after name

I tried setting up this project locally and ran into a few issues - https://github.com/docker/for-mac/issues/5864 - Compiling Nokogiri on M1 - https://nokogiri.org/tutorials/installing_nokogiri.html#how-can-i-avoid-using-a-precompiled-native-gem - https://github.com/sparklemotion/nokogiri/discussions/2359 - Ruby 2.6.6 is EOL -...

I opened https://github.com/hackclub/api/pull/483 to comment out everything in `heroku_scheduler.rake` and also went through the heroku dashboard to remove everything from the scheduler

Changed title to reflect what we ended up doing instead of upgrading postgres

Still in the process of reviewing this, but I wonder if CI is failing because you made this PR from a fork similar to https://github.com/ngi-nix/ngipkgs/pull/163 . The error message isn't...

I pushed up https://github.com/ngi-nix/ngipkgs/tree/libresoc-history-cleanup which replaces https://github.com/ngi-nix/ngipkgs/pull/168/commits/416a9410d561d543c4e73ecc677dead951770b95 with `git mv` when relevant. Many of these got almost entirely rewritten anyway, but `git blame pkgs/by-name/libresoc/verilog.nix` or `git blame pkgs/by-name/libresoc/pinmux.nix` should be...

> The git repos of Libre-SOC (https://git.libre-soc.org/) seem to be down. Obviously, without them nothing works. Maybe we could ask in their mailing list I was also seeing intermittent 502s...

> 2b. Include monorepo in this repo > > CC @albertchae, who had this suggestion to effectively fork the upstream monorepo into this repository. @jleightcap To clarify I didn't mean...