The senior dev on my team github.com/mcansh showed this to me. Super useful!

just published a new package. still not experiencing the aforementioned issue
github.com/stephansama/...

just using github actions with changesets. my token expires middle of february

github.com/stephansama/...

I have a decently sized monorepo of npm packages I haven’t had this issue yet?

I’ve seen heavy snowfall but not a snow squall never heard of it before had to look it up lol. Stay safe!!

That’s amazing that they recognized you for your contributions. Your work speaks for itself ❤️💛💚

What would the benefit be? Are they not all the same. Just seems like moving the issue instead of solving the issue

The inherent laziness of vibe coders. I think that’s @antfu.me’s original issue is that the changes are quantitative and not qualitative

If you link your configuration I can help

My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.

This is what i use to help

github.com/nektos/act