Was ist denn der beste Git-Hoster der nicht Github heisst? Ich würde gerne mal testweise über den Tellerrand gucken.
Gitlab selber hosten ist raus, hab ich gerade wieder gemacht und für unlustig befunden.
Vertragspartner (und Server) sollten in Europa sein
CI/CD wäre fein, aber kein KO-Kriterium.
Stabile, langweilige, mittelständische Betreiberfirma wäre großartig.
Is it unusual for a #GitHub repository owner to accept PRs, but only by copy-paste-and-rewriting them so that the #git history doesn't show any contribution credit from anyone else? they've made modifications to be sure, but clearly by referencing my code.
I feel like I've been plagiarized, but is there some good reason this is done and I should calm down?
It's just nice have your work acknowledged in the git record, right?
@matt Sounds like a bad practice. Is the code actually open-source (does it have a proper license?). Maybe they want to keep sole ownership for possible future relicensing?
I’ve gone from using the git command-line exclusively to almost exclusively using Sublime Merge.
I basically just keep it open on its own monitor as a real-time dashboard of all my changes. That, and the ease with which you can stage hunks and lines, has improved the quality of my commits and also gives me greater peace of mind.
(Downside: it’s a commercial app and Linux support exists but isn’t first class. e.g., doesn’t automatically respond to light/dark mode changes.)
@frigidcode There’s a preference for flipping between light and dark mode but it doesn’t do so automatically. In fact, it’s the only proprietary app I use on my system and it’s the only one that doesn’t do this. 🤷♂️
@aral I use it in similar way. I like the staging by hunk/line feature as well. It's much fast than via cmd (I know this hurts for cmd fanbois). Getting the overview over what has currently changed and what a selected amount of commits have changes is very nice as well. The commits, rebase and branching I still do via cmd though.
Concerning my toot from a few days ago concerning more "well-bounded" #dvcs patch workflows, I just discovered #pijul, which seeks to make applying changes commutative (ie the order doesn't matter) based on "theory of patches", "merge correctness", "partial clones" and "first-class conflicts":
"In Pijul, independent changes can be applied in any order without changing the result or the version's identifier. This makes Pijul significantly simpler than workflows using git rebase or hg transplant. Pijul has a branch-like feature called "channels", but these are not as important as in other systems. For example, so-called feature branches are often just changes in Pijul. Keeping your history clean is the default."
So someone made a commit with a future date to #LLVM. As a result, #git now produces a snapshot with dates in the future. Upon running #CMake on files from that snapshot, #Ninja keeps detecting that generated CMake files are older than their sources and rerunning CMake in a loop. Sigh.
We should mention that 2023 marks I2P's 20th Birthday.
🎉 HAPPY 20th BIRTHDAY I2P! 🥳
Privacy advocates and #freedomSoftware lovers with programming experience can help this historically significant project by grabbing a copy of the source code and contributing to its #security.
Together we can ensure I2P continues another 20 years.
I'm hosting my own Git instance for a while now (Gitea) and I'm still not sure if I want to have it as my default/main instance or stick with GitHub as my main.
What would you do?
I'm also very curious what self-hosted instances you guys use.
@chihuamaranian I just checked it out and looks also very promising, sadly because I have it running behind Cloudflare I can not directly push packages to it I had to disable Proxy from Cloudflare to check it out and so far I'm actually happy with the result =D