This is detailed, step-by-step instructions of getting this set up, with screenshots to help with commands and outcomes. An "idiot's guide" if you like, because I was that idiot.
Right now my "default" is to go to GitHub, and then maybe GitLab and Codeberg...but that leaves out all the other hosts out there. Once #ForgeFed happens we'll need it even more :fedi:
(By the way, I say "git" because that's where most code is, but if other kinds of repos are supported, even better! 🔍 )
I wish that when I reverted a revert, #git was smart enough to attribute things to the original author.
That is, person A does a commit; git blame foo.c shows the lines as being changed by person A. Person B reverts that commit (temporarily), and then later on person B reverts the revert (thereby putting person A's changes back in). But now when you git blame foo.c, the line change is from person B.
[I know you can manually set --author or whatever, but I feel like it should be automatic.]
@Andres4NY love doing git blame and seeing a commit you recognize from when whoever turned the repository upside down and you need to run the blame again with that number^^ 😂
with Xcode 14 I could hit ⌘⌥C, immediately type a commit message, then hit ⌘-return to complete the commit. git and I were both happy doing commits quickly.
with Xcode 15 I apparently have to first mouse click into the spot for the commit message... then I have do another mouse click on the Commit button.
Is there a way to set this back to the previous behavior?
#git and other source control repo maintainers: please add a blurb to your readme that explains what it is your product is supposed to do. Please start with explaining what problem it solves.
A clean Git history is the key to successful teamwork and quick bug fixes. Errors can only be successfully tracked down if it is always possible to trace when and where code was changed by whom and for what reason.
🥴 However, in the rush of the battle, the changes that are packaged in a commit are sometimes not taken very seriously. Who has never experienced this? A change that is actually unrelated to the current work package has made it into the commit because the file has already been saved temporarily.
💡The solution: With an "interactive add" (git add -i), you can pack partial changes ("hunks") into a commit and specify line by line what should be included in the next commit.