Live data from Hacker News

Private profiles are now generally available on GitHub

github.blog

61–70 of 70 posts

Re: Private profiles are now generally available on GitHub

#61

Earlier quoted context omitted.

It is great but last I used it there wasn’t any kind of free tool like dependabot built in.

https://gitlab.com/dependabot-gitlab/dependabot Haven't tried it yet, though.

Renovate is more complete and fully open source.

https://renovatebot.com/

But you will need to self host it, the included dependency checks in GitLab are paid.

However renovate has a free hosted version for GitHub.

Re: Private profiles are now generally available on GitHub

#62

Just in time for Netlify to discontinue support for private GitHub repositories for free plans. Good thing cloudflare still has free Cloudflare pages support for private GitHub pages.

In terms of features, CloudFlard Pages wiped the floor with the competition, nobody is even close.

Unless you care about centralization, then you might still use GitHub Pages or Vercel.

Re: Private profiles are now generally available on GitHub

#63

Earlier quoted context omitted.

https://gitlab.com/dependabot-gitlab/dependabot Haven't tried it yet, though.

Renovate is more complete and fully open source. https://renovatebot.com/ But you will need to self host it, the included dependency checks in GitLab are paid. However renovate has a free hosted version for GitHub.

While it may be "fully open source," watch out for its license:

https://github.com/renovatebot/renovate/blob/main/license

> Renovate versions 12.0.0 (released 2018-04-09) and onwards are released under the GNU Affero General Public License.

The dependabot-gitlab project mentioned above is MIT, for comparison

Re: Private profiles are now generally available on GitHub

#64
post #52

Earlier quoted context omitted.

Do you have a link to where they've said that, that really sucks, I've had a much smoother experience setting up pages with Netlify than Cloudflare.

Most people got confused with the wording in their recent policy change for the free plan. They recently changed the policy for Organization-owned repos. The continuous deployment for organization-owned private repos is no longer allowed in the free plan. But personal account's public and private repos are still part of the free plan.

Ah that makes a lot more sense. Thanks!

Re: Private profiles are now generally available on GitHub

#65

Earlier quoted context omitted.

You can make code public and still legally restrict its use (see: GPL).

GPL doesn’t restrict you from using it as input to a model. It’s just that as the model is a derivative work, it also has to be released under the GPL.

FWIW GPL was an example, I honestly don’t know whether it applies to the particular case.

Re: Private profiles are now generally available on GitHub

#67
post #63

Earlier quoted context omitted.

Renovate is more complete and fully open source. https://renovatebot.com/ But you will need to self host it, the included dependency checks in GitLab are paid. However renovate has a free hosted version for GitHub.

While it may be "fully open source," watch out for its license: https://github.com/renovatebot/renovate/blob/main/license > Renovate versions 12.0.0 (released 2018-04-09) and onwards are released under the GNU Affero General Public License. The dependabot-gitlab project mentioned above is MIT, for comparison

Disclosure: Renovate author

Renovate is indeed AGPL, but if you're just running it as a CLI, do you think there's anything to "watch out for"? It does not make any project you run it against AGPL, that's for sure.

Also you should be aware that dependabot-core, which dependabot-gitlab wraps, is not technically Open Source at all: https://github.com/dependabot/dependabot-core/blob/main/LICE... Wrapping a non-open source project in another project which claims to be MIT licensed does not change the underlying license. I'm not a lawyer but question the validity of them doing this without larger disclaimers.

However, I think that it's likely not something to "watch out for" either. Likely both licensing approaches were intended as a way to forbid or discourage competing services and each project welcomes people self-hosting.

In short I don't think that the license of Renovate or Dependabot is likely material for anyone planning to run it for themselves.

Re: Private profiles are now generally available on GitHub

#68

Earlier quoted context omitted.

https://gitlab.com/dependabot-gitlab/dependabot Haven't tried it yet, though.

Renovate is more complete and fully open source. https://renovatebot.com/ But you will need to self host it, the included dependency checks in GitLab are paid. However renovate has a free hosted version for GitHub.

What do you mean by "the included dependency checks"?

If you're referring to Renovate, there's no such paid option.

If you're referring to GitLab paid features, I'm not sure how that's any different between tools.

Re: Private profiles are now generally available on GitHub

#69
post #13
post #6

While looking over my GitHub account settings just now, I noticed that you can now designate a successor: > By clicking "Add Successor" below, I acknowledge that I am the owner of the @ttmc account, and am authorizing GitHub to transfer content within that account to my GitHub Successor, designated below, in the event of my death. I understand that..." https://github.com/settings/admin

This has been a thing for years and years.

About 2 years:

https://github.blog/changelog/2020-05-11-account-successors/

Re: Private profiles are now generally available on GitHub

#70
post #67
post #63

Earlier quoted context omitted.

While it may be "fully open source," watch out for its license: https://github.com/renovatebot/renovate/blob/main/license > Renovate versions 12.0.0 (released 2018-04-09) and onwards are released under the GNU Affero General Public License. The dependabot-gitlab project mentioned above is MIT, for comparison

Disclosure: Renovate author Renovate is indeed AGPL, but if you're just running it as a CLI, do you think there's anything to "watch out for"? It does not make any project you run it against AGPL, that's for sure. Also you should be aware that dependabot-core, which dependabot-gitlab wraps, is not technically Open Source at all: https://github.com/dependabot/dependabot-core/blob/main/LICE... Wrapping a non-open sourc…

Thanks for weighing in, and for drawing attention to the wrapped nature of dependabot-gitlab -- I didn't drill down into their implementation

As for the "watch out," I apologize if that came across as scolding or whatever, but in my company, and likely quite a few others, AGPL software is forbidden. Thus, maybe I have said "be aware" instead of "watch out," so I'll try to choose more neutral advisory language next time

Your "but it's just a CLI" is the nuance of the AGPL that I don't want to pay lawyers to disambiguate since this very thread was about running a GitLab bot, over the network, or in CI which is hosted on runners that connect over the network

Maybe I just need to stay out of these threads and let people do their own license homework, but I certainly do get value when someone else makes me aware so I can dismiss the tooling. No good deed goes unpunished, I guess

Post reply on HN