Github even bought Dependabot last year, so it's now free.
2,611 karma · joined December 12, 2012
[ my public key: https://keybase.io/wildpeaks; my proof: https://keybase.io/wildpeaks/sigs/yQmAnhmw5ODzOpfBpYvX1T7owc-Fwoe6TpMkU8-94Ho ]
Github even bought Dependabot last year, so it's now free.
- keeping an eye on future evolutions: each notification doesn't matter much, this is more about trends
- smaller (or merely private) repos where every single notification is extremely important
Now the big repos drown the small important ones, and each page shows less actionable information at a glance, so it takes longer to do the same things, and it's easy to overlook something important.
I wish they replaced it by tokens tied to specific repos and with scopes instead of that new Webapp Flow thing that looks a lot more complicated to implement than a curl request (I had planned to look into it this month, but obviously other worldwide events took priority).
With the benefit of hindsight, I'd highly recommend it and confirmed my suspicion that my queries weren't the problem, unfortunately.
It also showed queries are usually only advanced topics as one of my other habits (writing down summarized information in my wiki) lets me usually skip searching online for low-hanging fruits or information I already encountered.
I like keeping things small because it delays having to add complexity (and simple is easier to maintain, especially when you have better things to do) and saves on bandwidth.
Of course I'll keep evaluating new versions as they come (given nothing is sacred in my pipelines), so that might change in the future.
You can even remove replies as well: https://twitter.com/search?q=filter%3Afollows%20-filter%3Are...
Currently the closest equivalents are making a request via the API (but then you need a token with it, and all the security concerns it opens) or sending a special message using an empty commit (but I haven't found a simple way to do that from inside VSCode, unless I missed it somewhere).
I almost wonder if it's not a troll account given most of his repos are forks and his profile links to a website that doesn't load.
Also, a centralized command in the package manager enables generating lists that their accounting department can use, it can even be part of their automated pipelines and taken into account when they're billing projects to their users.
For larger companies (the ones that are most likely to afford this), making it easy for a problem to go away often matters more than the price itself.
But here's an idea instead: we already have a Sponsor feature on Github, so how about a command in the package manager that lists all packages that could be sponsored, similar to how packages can be audited ?
That way everyone in on an equal footing instead of money going to money.
And if it's not enough, how about using private repos where you need a subscription to access the package ?
Although I wish the documentation wasn't just PDF files you can't copy/paste from, not an ideal way to provide code snippets.