Everyone has a test environment. If you’re lucky you have a production environment too.
Everyone has a test environment. If you’re lucky you have a production environment too.
I only glossed over it… but this looks like it’s trying to check dynamic typing issues? It’s like a statically typed language with extra steps?
Fibonacci indentation of course.
Why not git clean -dxf
?
I read the lint part and my brain forgot about everything else. You could stick the danger call in a pre commit hook though.
Depending on which stack you’re using, you could use https://danger.systems to automatically fail PRs.
Was woodworking another common one?
We’re running home labs because we’ve learned that relying on “free” services eventually comes back to bite you.
If you ever want to bullshit a junior, use the git man page generator
Updated hyperencabulator https://m.youtube.com/watch?v=5nKk_-Lvhzo
I like to rebase on my feature branches before the PR because it’s a gift to my future self that resolves all the conflicts (if any) before my work goes in. I just find trying to figure out how those conflicts got resolved when there are a bunch of merges in more difficult if there’s a problem later. It’s easier to understand for me. YMMV, this does not work for everyone. Etc etc.
You can use Apple Configurator if you just want basic device supervision. IIRC it should be free. https://support.apple.com/en-ca/guide/apple-configurator-mac/welcome/mac
===
is just ==
with extra steps
Luckily they had lizards in stock.