3 ms·

Question: What did,"https://api.github.com/repos/actions/docker/tarball/76ff57a https://api.github.com/repos/actions/docker/tarball/76ff57a" had anything to do

Question: What did,"https://api.github.com/repos/actions/docker/tarball/76ff57a 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 ?

namanaggarwal 5y ago
So, OP has answered it and I missed it, Github shares commit hash between Forks and parent repo
- justusthane 5y ago
  Yeah, and it can lead to fun things like this: https://news.ycombinator.com/item?id=24882921 https://news.ycombinator.com/item?id=24882921
daniel-thompson 5y ago
> 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).
brilee 5y ago
It's a space-saving mechanism; since forks are extremely common, sharing commit trees across all of GitHub makes the forking action very cheap.
canadianfella 5y ago
*have