Many teams work exclusively in GitHub (ticketing, boards, workflows, dev builds). People also have entire production build systems on GitHub. There's a lot more than git repo hosting.
It's especially painful for anyone who uses Github actions for CI/CD - maybe the release you just cut never actually got deployed to prod because their internal trigger didn't fire... you need to watch it like a hawk.
None of those words appear in the article. I can deduce that the author of this article would never return a wallet. If they are this perplexed at the good deeds of others, and need to turn to science for a reason, they are as dense as a brick.
Reasons:
- because kind strangers have empathy
- because kind strangers want to do what is right, and help others
- because kind strangers would hope the same thing is done when they lose their own wallet
Lines with actual code changes aren't a problem for me, it's the automated IDE indent/spacing/bracketing that really drives me up a wall and fatigues the hell out of me.
But this might only be a problem with those of us working on legacy codebases. The kind of PRs I see in OSS projects I could review 1000 lines at a time - it's so clean!
Yeah, it's really something that you have to get buy-in for.
You could always make a commit that just has the reformatting when you do start editing a file. If it turns out you didn't need to edit that file after all, then you can revert just that commit easily. And if you did, you can collect up all the reformatting commits into a PR as a first step.
The flip side of this is making minimal surgical small changes, and then doing the refactoring after the change. The key message though is split them.
Refactoring doesn't change behavior, so refactoring efforts should be judged only on "tests exist that cover the functionality, those tests continue to pass, the code is easier to maintain". It's when you add "changed functionality, so we changed the test" to review at the same time, that this becomes a hassle.
It bit Mozilla users harder because Mozilla uses "DNS over HTTPS" to cloudflare itself, ignoring your system DNS. There's a setting to change that but you have to enter "DNS" in the "setting search" to get it.
I imagine some OSS authors don't consider someone visiting the GitHub readme before visiting their website. I can't fathom thinking like that, but it must have never crossed their mind.
You can watch the matche videos from training runs: https://www.youtube.com/@Sscaitournament/videos
I don't think BWAPI has ever integrated modern AI models, but I haven't followed its progress in several years.
reply