4 ms·

Was there a guard needed? I don't think so. It seems GitHub didn't saw any degraded performance and barely noticed the issue, and odds are they presumed the aut

by rewmie 3y ago

Was there a guard needed? I don't think so. It seems GitHub didn't saw any degraded performance and barely noticed the issue, and odds are they presumed the author screwed up with their GitHub actions configuration. Once they determined it was plain old abuse, I'd guess some GitHub employee said "what a moron" and proceeded with his day.

eyelidlessness 3y ago
What are you basing this on?
- rewmie 3y ago
  > What are you basing this on? To start off, based on the fact that GitHub is around for over a decade and this was the first time this sort of attention-seeking stunt was made public. Do you have any indication this sort of stunt is relevant?