4 ms·
It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed t
by avtar 6y ago
It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.
- markrages 6y agoWhat was Admiral Ackbar's famous quote?
- nemosaltat 6y agoIt’s an exception?
- whycombagator 6y ago“ask yourself if that answer doesn't make you look just a bit like a dewback's cloaca”
- anonova 6y agoWhich is funny too because GitHub repos have Docker repository functionality: https://github.com/features/packages https://github.com/features/packages But since its release, you still can't do public pulls: https://github.community/t/docker-pull-from-public-github-package-registry-fail-with-no-basic-auth-credentials-error/16358/2 https://github.community/t/docker-pull-from-public-github-pa...
- myroon5 6y agolooks like it's changing now: https://github.com/github/super-linter/pull/137 https://github.com/github/super-linter/pull/137
- sdesol 6y agoGitHub's Super Linter has an unusual history. See below for example: https://imgur.com/KZ008vu https://imgur.com/KZ008vu https://imgur.com/yJSHIWS https://imgur.com/yJSHIWS admiralawkbar accounts for 80% of the commits in the repository and over 98% of the code churn. I'm guessing this was a side project of his (Lucas Gravley aka admiralawkbar) and the docker image was just something that was overlooked when it became an officially advertised GitHub repo.
- zkoppert 6y agoYup, thats exactly what happened.