@sophie
Got some consequences often enough as some commands where changed and most of my pipelines stopped working 😀

@sophie @drew

GitHub consequences happen whether you're ready for them or not.

@sophie I feel like this is already my life

@sophie have they switched thr API verbs to “fuck around” and “find out?”

@sophie github fuck around and github find out

@sophie ah yes, the bill!

@sophie github consequences is what happens when you decide to look at the self-hosted runner source code 🦋

@sophie followed by Sourcehut fucking around and finding out.

@sophie github IS github consequences

@sophie
Aren't they called "artifacts and logs"? 😏

I'm more looking forward to see how the 3rd law of motion applies on Github Actions 😅

3rd Newton's Laws of Motion: "For every action, there is an equal reaction but in opposite direction".

@sophie GitHub finding out

@sophie "Prepare for... uncommited consequences" - the GitMan

@sophie
Code around, debug out
@rail_

@sophie the github consequences of doing github actions is losing your github sanity

@sophie as someone who largely maintains GitHub actions as my day job, I can assure you that GitHub consequences are well and alive 😂

@sophie fork around and find out

@sophie been facing these every day 😭

@sophie automated Fuck Around/Find Out pipeline

@sophie yes.

And I've taken those multiple times!
https://github.com/greyhat-academy/lists.d/blob/main/users.github.block.list.tsv
https://github.com/greyhat-academy/lists.d/blob/17f74bcd3432024657145e037225dfd83af2d28b/users.github.block.list.tsv#L3

@sophie GitHub copilot

@sophie I think those are called "CI artifacts".

Gonna start calling them "build consequences" now lol.

@sophie fork around and find out.

@sophie this is awful and i love it

@sophie No but I have GitHub Thoughts and Prayers. Does that help?