I haven't looked at the GitHub API in a long time but I wonder if it would be possible for a 3rd party to replicate this functionality using the GitHub API.
Yes, quite easily I’d suggest. I’ve built a GitHub analytics tool on top of their api. Primarily for internal metrics & tracking community engagement. The api makes a lot available, it’s very open. For public repos you can get lots of stats around activity and community engagement that would enable monitoring/projecting growth.
This is a really simple script that I use to save a few keystrokes when I'm querying a package.json from the CLI. It depends on JQ. e.g., pkg dependencies, pkg version, etc.
#!/usr/bin/env sh
set -o errtrace; set -o errexit; set -o pipefail
if [ -n "${1}" ]; then filter="${1}"; else filter=''; fi
jq ."${filter}" package.json
Acronyms can make sense to switch case, but initialisms... en-pee-em... I guess it happens. I originally was introduced it as Node Package Manager, but I'm gonna make an effort to correct this now.
Had one as a kid too. It was my intro to video games so I've got fond memories of it. It's funny I had a lot of fun with the games but didn't realize until years later that a lot of the games we had were just clones of more popular games.
I'm aware of it. Hasn't been updated in a long time, and you need to otherwise install vagrant and a VM manager separately (fortunately, it doesn't ironically tell you how to do so via homebrew...)
I think a first-class vagrant app for Mac OS would (a) be available in the App Store for simplified VPP deployments (b) install vagrant and (c) either come with a lightweight VMM over Hypervisor.framework and/or work with other active VMMs like Fusion, Parallels or even Docker Desktop.
Vagrant was born of the CLI, but I think in 2021 it needs to embrace its role as a bridge between the GUI and CLI. Just my opinion, though...
