Kennt ihr #Git? Auch wenn ihr kein(e) Programmierer:in seid, dann seid ihr bestimmt schonmal auf #GitHub, #GitLab o.Ä. gestoßen. Auch als Designer:in, Maker:in, Texter:in oder einfach nur zum Projektmanagement spielen Git und die dazugehörigen Plattformen heute eine große Rolle. Wir erklären Git/GitHub/GitLab für Nicht-Programmierer in einem dreistündigen Workshop am Sonntag, den 19. Mai. https://www.welcome-werkstatt.de/veranstaltungen/git-fuer-nicht-programmierer
PSA: Do not submit "omnibus" pull requests to #git repos, especially without talking to the maintainer first. Keeping PRs generally focused to one particular problem or feature makes things far more manageable for reviewing, testing, and reverting/bug-fixing later on. I would always much rather have 10 smaller PRs focused one specific thing each than one massive unsolicited one with a bunch of scope creep.
It's a big mix of small and medium-sized changes:
– A spiffy new welcome window, with recent repos
– You can now open a special example repository for testing things, that resets when you close its window. Go nuts!
– Check the global Git config using the sensibly-formatted table in Settings.
– Never forget about a rebase again: Retcon shows a big obvious badge in the Dock whenever you're paused for editing.
@jrf_nl I have the same technique! I make the messy commits on a branch called sandbox-something and then git merge --squash to either main or a feature branch if it's just one step of many. #git
BitMover's closed-source product, BitKeeper, was used for source control for the #Linux kernel. Larry McVoy, CEO of BitMover, was upset because someone tried to figure out how the BitKeeper worked and he pulled the BitKeeper licenses from Linux developers.
Needing distributed source control, Linus Torvalds created #git in a couple of months.
BitMover is gone and BitKeeper is now open-source, gathering dust, in a git repository.
Opinion: people who staunchly prefer working with Gerrit, and consider anything else inferior, really love working with git-review. And if git-review were not Gerrit specific they would be just as happy with, say, GitLab.
The process that the git-review/Gerrit combo automates/enforces (one commit per change, automatically generated topic branches, change IDs with cross-project uniqueness) could also work just fine by hooking up git-review with the GitLab API.
If you’re working on Kitten¹ from source, please clone a fresh copy.
I just rewrote history to reduce the repository size (correctly this time, including all references from branches, tags, etc.).
The good news is that – contrary to what the Codeberg interface is currently showing the size to be (176MB) – the repository is only about 5MB now so it should only take a couple of seconds to clone.
Trying and learning different bug tracking and project management tools for the last few weeks (bugzilla, debbugs, track, redmine, gitlab, taiga, plane, forgejo, phabricator, gitea, sourcehut and a couple more) I have to admit that the most convinient, visually pleasant and functional enough is GitHub Projects :/
Adding a “Git config options” table to Retcon, for seeing current values.
When an option isn't set, the app tries to be helpful and shows the actual resolved value.