All these comments and no one is going to point out that this is invalid?
The git stage and git commit don’t have any terminator, so it’s all one “command” and will fail. Then there’s a single & between git commit and git push, so it would run in parallel, so it would also fail.
Also, don’t git stage . people. Or at least do a git status before to make sure you didn’t stage file-with-all-the-production-secrets
Rereading it, I now understand what you meant. I interpreted the “like regex” as an example of advanced git knowledge. I’m not sure the comma helps make it unambiguous though.
Yeah, reading it again and I can see that interpretation…
This is why you shouldn’t rely on yourself alone for proofreading your writing, I probably could have read that a hundred times and not seen another way to read it without someone else pointing it out
I’d volunteer, but can’t rightly say I’d keep an active programming.dev account. Sadly none of the clients I use would alert me to new things on it, so I’d likely forget to check.
programming.dev will migrate over to (lemmy compatible) Sublinks once it’s ready, which will feature a different set of mod features. For that reason we will need new moderators to have an active programming.dev account. If you’re willing keep an active user account on our instance let me know. We would prefer people we know will actively use their mod account to make sure reports are handled in a timely manner.
With automated CI, I’ve had very few times where bisect is useful. Either the bug was introduced 1-2 commits ago, or it’s always been there and the exact commit is irrelevant to the solution, since you just fix it forward.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.