this post was submitted on 07 Jun 2024
532 points (98.4% liked)
Technology
59979 readers
3950 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you have your secret keys in your repository you've already fucked up, long before you accidentally make that repository public.
And that’s why you always ~~leave a note~~ recheck your .gitignore file before committing
Does Microsoft's GitHub offer any pre-receive hook configuration to reject commits pushed that contain private keys? Surely that would be a better feature to opt all users into rather than Windows Copilot.
They notify but iirc only if you push a commit to a public repo. The dev in the article pushed it to a private repo, then later made the repo public.
The docs say they can reject if you enable push protection, which is also available for private repos, just as a paid feature. It's free for public, but still needs to be enabled.