[lerno]

One funny thing is that if you go on codeberg and want to submit a PR to Zig, you can't. Because Zig's too big for Codeberg, and you're over your free quota, so you can't push your update to your fork.

Yes there are ways around it if you have patience, but what the heck!!

[stock_toaster]

> Yes there are ways around it if you have patience, but what the heck!!

https://forgejo.org/docs/latest/user/agit-support/

[mlugg]

Worth noting that while it's absolutely unfortunate that we're hitting this Forgejo design flaw, AGit honestly is just a better workflow, and I (Zig core team member here, full push access to the upstream repo) have started using it for pretty much all of my PRs. There are a couple of small things I'd like to see improved about Forgejo's implementation of AGit, but IMO it fundamentally makes so much more sense than the two-step push-then-PR workflow (especially if you're an external contributor who would also need a first step of "fork the repo").

[stock_toaster]

I agree. It would be very interesting to see a forjego config-mode/fork/clone/alternative with AGit as the main (or _only_) contribution workflow!

[lerno]

Yep