Tell HN: GitHub will delete your private repo if you lose access to the original • Hacker News Board

Re: Tell HN: GitHub will delete your private repo if you lose access to the original

#291

Post by jzb » Fri, Feb 03, 2023, 12:53 AM UTC

charcircuit wrote: post #219

jzb wrote: post #98

Earlier quoted context omitted.

It knows the license applied to the repository. For a private repo it may not be "released" under that license but planned for release. If AcmeCorp is planning to release - but hasn't - a project under MIT or whatever, they may have the license declared in the repo but that's not a guarantee it's ever going to be released. If it's a private repo, and your access has been under your status as an employee, then I don't…

Software can be open source and not released. Employees can legally release it themselves since it is open source.

Really no. The employee doesn’t have that right, it’s not theirs to release unless the employer gives permission.

Re: Tell HN: GitHub will delete your private repo if you lose access to the original

#292

Post by remram » Fri, Feb 03, 2023, 9:10 PM UTC

saltcured wrote: post #290

remram wrote: post #284

Earlier quoted context omitted.

But that's... exactly what I described and asked how to avoid...

I had trouble parsing your earliest comment, so I only tried to address the incremental backup concern. I may not have understood the conversation, but it seemed like you claimed that a filesystem level backup of a clone was not going to produce incremental backup IO in practice. A periodic fetch into a persistent cloned repo will be incremental unless the upstream is doing something crazy with frequent branch deleti…

Again, this requires you to have a persistent clone on a filesystem. I specifically wonder if we can do (and I quote) "direct incremental git-to-S3 backups", and you keep replying "it's easy, do it indirectly with a persistent cloned repo".

I don't understand where you are stuck, tbh.

yencabulator has provided a good tip I think, as you could store the previous set of refs and use that to build an incremental Git bundle (one with only the objects that were not in the previous bundle). I don't know if you can do that with the existing Git client though.

Re: Tell HN: GitHub will delete your private repo if you lose access to the original

#293

Post by jmondi » Fri, Feb 03, 2023, 11:49 PM UTC

mckn1ght wrote: post #283

jmondi wrote: post #183

Earlier quoted context omitted.

I wrote a little tool to mirror my repositories to my gitea instance. It has been months to potentially a year or two since I ran this, but it does what you’re asking. You can mirror repositories of users and repos users have starred. It definitely needs some love. https://github.com/jasonraimondi/deno-mirror-to-gitea

I wrote a similar one I called Forgery that’s in a repo of the same name in my github account (which can be found in my user profile… just created this account and didn’t want to post a link in my first post, thought it might get automodded). Very similar to yours, but also does forks, which I’m not sure yours does by a quick glance at your readme. Although, mine doesn’t automatically mirror from another forge, just…

If I remember correctly, I believe that mine will do forks also, they are just included in in your repositories.

I just looked over your project, and it seems pretty cool. A little bit different than mine, since mine is specifically github to a gitea mirror repository. I don't mind adding a link to your project in mine.

Thanks for sharing!

Re: Tell HN: GitHub will delete your private repo if you lose access to the original

#294

Post by kitkat_new » Sat, Feb 04, 2023, 8:57 AM UTC

IncRnd wrote: post #289

kitkat_new wrote: post #270

Earlier quoted context omitted.

I am not trying to construct anything. I just described what happens and what I expect. "where you have the ability to elevate your own rights to somebody else's repo's contents." This is not an accurate description. There are two repositories: the original repository, and the fork. Nowhere I want to to elevate my rights regarding the fork to the original repository. " Name a computer system that intentionally allows…

You keep trying to claim that a different person's private repo that you have forked has somehow given you ownership over the contained information. That's just not the case. Forking their code doesn't make it yours.

actually that is the point of a fork onto my account