I came across a stack overflow recently about how to do something in a jasmine unit test. Someone gave a solution of “I just changed the test to xit(“… and now there are no errors!”

No, but you can see the megawave in this photo

It would just get closed. They are strict about GitHub issues ONLY being for actual issues/bugs you find with that project. Anything else is either closed as not being an issue

There are several projects on GitHub I use that are sometimes hard to find answers for questions. They have closed the Discussions on their GitHub page, and if you ask a question by opening an issue they close it and say “go join our discord server”.

It’s frustrating. You can’t search online for any issues. When you join the discord server, you can search and find lots of questions, but there are very few answers.

I think you just have to open those sites and turn off notifications for them. I would hope there’s a more fine grained option somewhere to say “only when the tab ids open” but if there is, I don’t know about it.

SourceTree by Atlassian is great, I’ve used it for years and love it. It’s also free. They kind of push you into signing up for a BitBucket account, but it’s skippable. I think it checks all the boxes for the requirements you listed.

This same advice is true for the JavaScript situation as well sometimes

Frank Underwood for re-election

I am a native English speaker and I have never heard this phrase before, so don’t worry it’s not you!

This has happened a few times were I find a solution on stack overflow, I go to upvote the answer and I get the error message “you can’t upvote your own post”

Yep, that was my answer to my own question from 5 years ago

Costumers?

Oh no, who could have foreseen this?

I loved unlocking this level for multiplayer on Goldeneye

I made a branch, make commits, and then make a PR. I don’t care about the number of commits because sometimes a reviewer might be able to make more sense of a PR if they view each commit instead of all the changes at once.

For us we just make sure that the branch builds and passes tests before merging it in, and just do a general look over to make sure everything looks correct, follows best practices, etc. if the UI was changed I usually add screenshots of before/after or a screen recording of me using the feature. Sometimes these can really help a reviewer understand what all the changes mean.

include $pixels;

Woof woof

It’s all lies. Roundup tastes great, I’ve been drinking it for years. No problems.

Not all of them, no. Some are just to build or run development only tools.

And ribs, don’t forget about prime ribs

Thanks for this, it makes a lot of sense actually. Oh well, my mom has her car and the warranty she will hopefully never need, but it’s there if she does. I guess it all comes down to care tactics in the dealership, pressuring you to buy warranties and such that you may not need and cannot buy at any other time except right then.

I’ll be sticking with the recently used philosophy for the future though.