Comment by jachee 6 days ago They’re tab-completion with extra cognitive-load steps. 3 comments jachee Reply a_bonobo 6 days ago I mean, if you can solve 9% of Github issues automatically that's a fairly huge load of work you can automate. Then again you'd have to manually identify which 9% of issues. blibble 6 days ago "update dependencies"that would probably cover it, and you don't need "AI" to do that dboreham 6 days ago You do if it's a JS project because every patch release of every dependency makes breaking API changes.
a_bonobo 6 days ago I mean, if you can solve 9% of Github issues automatically that's a fairly huge load of work you can automate. Then again you'd have to manually identify which 9% of issues. blibble 6 days ago "update dependencies"that would probably cover it, and you don't need "AI" to do that dboreham 6 days ago You do if it's a JS project because every patch release of every dependency makes breaking API changes.
blibble 6 days ago "update dependencies"that would probably cover it, and you don't need "AI" to do that dboreham 6 days ago You do if it's a JS project because every patch release of every dependency makes breaking API changes.
dboreham 6 days ago You do if it's a JS project because every patch release of every dependency makes breaking API changes.
I mean, if you can solve 9% of Github issues automatically that's a fairly huge load of work you can automate. Then again you'd have to manually identify which 9% of issues.
"update dependencies"
that would probably cover it, and you don't need "AI" to do that
You do if it's a JS project because every patch release of every dependency makes breaking API changes.