Showing 1-30 of 100
Does this setting cause a problem where stuff like
PB&J sandwich@penny-processor how to encrypt all files in my repository right before every commit?
Boss loop exhausted 3 attempts. Auto-decomposed into 1 smaller sub-issues with
boss-ready@copilot resolve the merge conflicts in this pull request
I can't resolve these comments, so I'm just gonna reply "Done" to them.
Done
Attempt 1/3 failed on
mothershipv2.2.0 was released today. Nothing was changed again. :(
no need to cover this since it is impossible in production, we do not live that long before it overflows
"I have not read any of the above and just checked all the boxes to submit the issue"
Attempt 2/3 failed on
mothershipWe could use orElsethrow when user not found
TIL that for the date constructor the year and day are 1-indexed but the month is 0-indexed 🤦
Plan revised 5 times without approval (max 5). plans=5, implementations=0. Escalating to human.
The secret of tree-transform is that basically ALL of these are defensive and untested lol. I'd suggest not doing a code-coverage on these :D
The Collatz conjecture? Bold. We already have enough unsolved mysteries in this repo (like why our commits keep getting greener 🟩). But yes, let's do it! 🎲
can't, because there's some retarded code that sets it to null after copying a
CObjectoh this was an unused variable that instead of being removed was cast to void... yeet!
😆 I did not request this, but... it's a little too cheesy. Prob should remove it. But it's hilarious to me that this UX trend influenced Claude.
@copilot resolve the merge conflicts in this pull request
@copilot resolve the merge conflicts in this pull request
formatted using black
Please don't. It introduces numerous "changes" that change nothing, but make real changes way harder to find.
Did this guy really create a Github account just to harass the developers of a free software about a feature that he wants?
Seems comprehensive, do we need more threats? :)