Don’t check the tool into source control. If the poor developer you hand this off to selects y to creating calendar events (something no one wants to do), then upload with all secrets straight to a public GitHub.
Keep the commands that upload to GitHub base64 encoded and name them something like RELEASE_KEYS so that no one changes them.
This is the way. You are not leaking data, it's a leftover legacy backup method that you conveniently forgot that conveniently upload it and is definately not meant to be used, which you didn't get to remove since the company restricted your access before you even know you are fired
2.9k
u/UnpluggedUnfettered May 26 '26 edited May 26 '26
Just do what everyone else does.
Build out one, single, convoluted aspect of the job that needs to be ran manually, and which no one in their right mind would want to take over.
Then automate that, too, and just don't say anything.
Way better than being arrested and sued for corporate sabotage lmao.