How I accidentally took down GitHub Actions (2019)

Re:How I accidentally took down GitHub Actions (2019) by namanaggarwal on Friday July 09, 2021 @08:26PM (#27789970)

Question: What did,"https://api.github.com/repos/actions/docker/tarball/76ff57a" had anything to do with the OPs fork? Shouldn't it just point to the original repo which didn't had the clashing commit ?

[ Parent | on HN ]

Re:How I accidentally took down GitHub Actions (2019) by brilee on Friday July 09, 2021 @08:40PM (#27790066)

It's a space-saving mechanism; since forks are extremely common, sharing commit trees across all of GitHub makes the forking action very cheap.

[ Parent | on HN ]

Re:How I accidentally took down GitHub Actions (2019) by namanaggarwal on Friday July 09, 2021 @08:30PM (#27789990)

So, OP has answered it and I missed it, Github shares commit hash between Forks and parent repo

[ Parent | on HN ]

Re:How I accidentally took down GitHub Actions (2019) by justusthane on Friday July 09, 2021 @09:31PM (#27790342)

Yeah, and it can lead to fun things like this: https://news.ycombinator.com/item?id=24882921

[ Parent | on HN ]

Re:How I accidentally took down GitHub Actions (2019) by daniel-thompson on Friday July 09, 2021 @08:30PM (#27789991)

> However, I realized I could get around that issue by forking the actions/docker repo and pushing a commit to my fork (since GitHub shares commits between forks and parent repositories).

[ Parent | on HN ]