Conversation

Notices

1. Embed this notice
   SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 04:21:05 JST SuperDicq

   I wonder how many hours it's gonna take for our old guy "Jef" over here to realize how to git rebase this repository to remove all of the leaked shit.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 04:23:31 JST SuperDicq

     in reply to

     • :suya:

     @newt@stereophonic.space Who hasn't at this point 😂

   • Embed this notice
     :suya: (newt@stereophonic.space)'s status on Wednesday, 25-Sep-2024 04:23:32 JST :suya:

     in reply to
     @SuperDicq too late. Already forked, downloaded, and saved it.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 19:23:53 JST SuperDicq

     in reply to

     Update: He still hasn't figured out that the leaked code isn't actually removed from the repository.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 19:37:37 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org Wait so on Github you can still get commit hashes from a deleted repository? The more you know.

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 25-Sep-2024 19:37:38 JST Phantasm

     in reply to
     @SuperDicq You can't remove it. GitHub doesn't work that way. The only way for the code to be removed is to nuke the repository and all it's forks, because even if he deletes the main repository, you can still access all the commits from the repo by manually specifying the commit hash in the URL.
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Wednesday, 25-Sep-2024 19:47:06 JST 翠星石

     in reply to
     @SuperDicq Yes, if github was to ever actually delete any software, that would be an obstacle to the plan of collecting a bunch of software, shoving it through a in-exact heuristic compression program and having that program vomit out verbatim or combined parts, for integration with proprietary software.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 19:50:25 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org Github forks are not a standard Git feature and I'm very familiar with Git but I do not use Github.

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 25-Sep-2024 19:50:26 JST Phantasm

     in reply to
     @SuperDicq The fork functionality on GitHub works like a tree. If you have a fork of a repository and that fork lost its parent because it was deleted, that fork is now the parent of the tree. If you private a repo, all the previously public code can still be accessed from the forks and if you delete that private repo every public fork will still work.
     
     If you have a private repo and make it public, all the commits in the private repo are now public. The only thing you need is the commit hash to access them.
     
     There was a big kerfuffle about exactly this issue few months back.
     
     https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-public-repository-to-a-private-repository
     https://trufflesecurity.com/blog/anyone-can-access-deleted-and-private-repo-data-github
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 19:54:31 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org I think Github's fork + pull request strategy for contribution is not very efficient and creates a ton of problems (like the one you just described).
     
     I will never understand why people prefer this workflow over sending patch files over email (how Git was intended to be used).

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 20:04:15 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org You don't have to manually run CI if you just set up a git hook.

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 25-Sep-2024 20:04:17 JST Phantasm

     in reply to
     @SuperDicq There's many reasons why people prefer centralized forges like Github/GitLab/Gitea/Forgejo. You have the code, patches, issues and everything in one place. You don't need to search through Bugzilla/Jira to create/comment on bugs and then submit patches through email and download code from cgit. It's all in one place and neatly organized. Then there's also the fact that manually running tests on patches will become cumbersome when a CI/CD system like Jenkins or Gitlab/Github actions will do all of that for you.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 20:06:20 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org Creating git hooks isn't hard, and it just uses bash scripts which gives you way more freedom than the Github Actions yml format for example.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 20:07:55 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org I don't see how running them locally wastes time compared to doing it on a server. They still have to be executed. It's just that now a computer that you control is doing the work instead of a computer that is owned by Microsoft.

     翠星石 likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 25-Sep-2024 20:07:56 JST Phantasm

     in reply to
     @SuperDicq You still waste time by running them locally on your machine. Granted you can still do other things, but then you become sidetracked. A build or a CI/CD server can do all that for you, will be much more powerful then your dev system, can be on prem and most importantly will share the results of the pipeline with everyone involved.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 25-Sep-2024 20:09:10 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org And if you really want the work to be done by a server why not buy a server and install something like the sourcehut build system on it?

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 25-Sep-2024 20:10:49 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Phantasm
     @SuperDicq @phnt In fact you can use any language, like of course I got my sourcehut hook in Perl for my self-hosted git server: https://hacktivis.me/git/utils/file/git-hooks/post-update.srht.html
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 25-Sep-2024 20:17:02 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • Phantasm
     @SuperDicq @phnt Also SourceHut and I think few others like patchwork runs CI automatically on email patches, and power of email means it can be easily forwarded to any number of those things.