isbadawi

A workaround I've used sometimes to retrigger CI is to do `git commit --amend --no-edit --reset-author`. This changes the sha by changing the author timestamp. Then you can force push it to the PR branch

I think the person you're replying to is saying that "fully implement every unit test up front" does not describe TDD. With TDD you continuously alternate between writing tests and writing production code. It's not like you write a whole test suite up front.

There must be a typo somewhere in your comment, I don't understand how 350/week for 5 months is better than 500/month.

This seems to be covered by the new ability to extend issues with custom fields.

I guess you have to be careful not to return inside of these :)

I don't understand why you wouldn't be able to, especially given "a million years" to learn whatever you need to learn. Why does it feel inaccessible to you?

It makes sense to me that merge commits would "contain changes" (i.e. that a merge commit's tree would have content that is not in either parent's tree), otherwise how else would you represent the result of resolving merge conflicts?

ripgrep isn't a 1:1 rewrite of grep. It's a different program.

The government decides all the time that some people should be punished. It's the justice system.

What are these quotes from?