5 ms·
> No amount of back and forth is going to convince them that leaking commit messages on enterprise accounts is serious apparently. If true, this deserves a wri
by Cpoll 7y ago
> No amount of back and forth is going to convince them that leaking commit messages on enterprise accounts is serious apparently.
If true, this deserves a write-up.
I'm sure a few enterprise accounts might agree, if anyone can see their dev-branch commit named "feature xyz" a month before they announce it.
- chias 7y agoJoke's on you: trying to fix bug maybe this? fuck idk idk idk maybe works k ready now
- Cpoll 7y agoBut also: "fix stupid fucking sql injection"
- avianlyric 7y agoThis sounds far worse than just leaking branch names. They said it’s leaking entire commit messages. Those messages could contain very detailed descriptions of how a companies product works, or how a companies fraud controls operated.
- Cpoll 7y agoSorry, that's what I meant. I should rephrase: a commit message for a commit on the dev branch. I was assuming a relatively lazy commit message as an example. You're correct in identifying that certain organizations might put a lot of information into a commit message.