One does not commit or compile credentials
Context:
This meme was brought to you by the PyPI Director of Infrastructure who accidentally hardcoded credentials - which could have resulted in compromissing the entire core Python ecosystem.
this post was submitted on 12 Jul 2024
368 points (97.4% liked)
Programmer Humor
18961 readers
986 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This sounds like a really useful solution, how do you implement something like this? Especially with linter integration
I'm not sure, sorry. The source control team at work set it up a long time ago. I don't know how it works - I'm just a user of it.
The linter probably just runs
git diff | grep @nocommitor similar.Depending on which stack you’re using, you could use https://danger.systems to automatically fail PRs.
PRs? Isn't the point of
@nocommitthat something does not get committed, and therefore no credentials are stored in the git repository? Even if the PR does not get merged, the file is still stored as a hit object and can be restored.I read the lint part and my brain forgot about everything else. You could stick the danger call in a pre commit hook though.