>>109013966
Why the fuck would you do that? Just use something like Codex or Claude Code, and use natural language to do this shit. Nobody types git commands or ssh commands anymore

>>109013966
>For years I've been working on various kind of stuff and I've never had the slightest need for it.
Then you haven't worked on anything important.
>1) learn 2 entire languages (git and ssh) in addition to what I already need.
These are not languages and you only need to learn a handful of commands.
>2) having to sign up to some big corpo platform and properly connect my repositories using ssh keys.
Git is not GitHub. You can self-host it if you really want to.
>3) being forced to do additional tasks on command line when I didn't have any need to.
Good IDEs have git integration.
>4) constantly being aware of all additional levels of abstractions involved (working directory - staging area - stash - the verious branches) and God helps you if you ever happen to mess up.
None of this is true.
>5) even having to learn some retarded snowflake etiquette (such as having to comment every single thing you do, using "add" instead of "added") like I've joined some kind of cult.
If you're working on a project with specific guidelines you should follow those guidelines.

>>109013966
>don't try to learn something that will continue to benefit you if you can just menial labor it

why are so many people on 4chan making up random non-existing problems to whine about as if they were saying something intelligent

File: 1751945630553725.png (346 KB, 1280x1344)

346 KB PNG

>>109014050

>>109013966
For more centralized teams all working in the same product, I agree git has some unnecessary complexity. There are alternatives like p4 or mercurial.

But for complex codebases, some form of source control is vital. It lets you attempt to refactor things without having to worry about copying your entire source tree. It lets you remember why you made X change a year ago, and having history gives you context so you don’t make regressions. Of course unit tests and such help too, but it’s nice to have more than one kind of protection.

>>109014056
What's this lol?!?
Anyway, they mention /pol/ which is a containment board on its own. Why would they apply the same tactics here where the most controversial posts are about Windows vs Linux, C vs Lisp, etc?

git is very useful if you are working on one codebase together with other people, something you clearly never had to do.

It's also useful for solo development, but only for people who are not dumb.

>>109014081
you must be blind

>>109014081
because pol is already dead with bots and and paid shills. g is the only place where people talk against the current new agenda, total digital censorship.

>>109013966
you sure are fucking stupid lol

Don't fall for the bait thread

>>109013966
this >>109013980, just build aliases with agents? what year is it? do you have a job op?

>>109013966
This cheatsheet is total garbage and a noobtrap by the way. Anyone who follows basically any of these commands and think they know git are shitters who have never worked in a collaborative environment with git before.

>>109014050
>>109014056
>>109014142
>NOOOO stop complaining about cancer! That's le bait! You're pulling attention away from my precious AIsloppa & AIshilling threads!

>>109013966
Claude and Codex split and write my commits without them being meaningless LLM slop

>>109013966
Imagine getting filtered by a fucking git lmao. With all these git helpers like lazygit, when git is practically integrated in every IDE...

Yeah, Git is fucking useless.
For collaboration a simple system where a developer can "lock" a set of files would be far more useful.
>Hey guys, I'm going to be overhauling the XYZ subsystem, so no one else should change it while I'm in the middle of working on it.

>>109014806
I know you're joking about previous generations of popular VCSs but first, git is not the first dvcs and previous ones were better, and second, modern SVN is unironically infinitely superior than modern git (which is infinitely superior to ancestral git).

>>109014645
>having to use industry standard tools is..... cancer

>>109014826
>modern SVN
The only reason I've seen for this is
>commit and push are a single action
Sure git doesn't have the best defaults but can you name a single thing svn does better?

Why does git insist that I enter my real name and email address if I want to commit to a remote repository?

>>109014056
>19year old parajeet tard posts are a part of sophisticated elaborate plan employing AI and....

>>109013966
I will skip insulting you since you've obviously never worked on a professional team.
But in return you should swallow a humble pill and admit that you don't know shit.
It's quite obvious which problems would arise from several people working on the same codebase at the same time.

>>109015160
Also git is piss easy. There are only a handful of commands you actually need.

>>109013966
That sheet is really outdated and poorly designed (which way does the arrow go, lmao). To the noobs: learning git will continue to be useful and the commandline is the best way.

>>109015107
it doesn't. who is going to verify it's your real name?
you can enter Donald duck if you want.
you don't need an email either. you're confusing GitHub and git.
of course GitHub will need some type of credentials.

>>109015077
Not at all. Separate versioning per-file makes revisions, large assets, and monorepos infinitely easier.

>>109015207
Github requires exactly as much and no more credentials than git itself does. He's referring to git config, without which you're not allowed to push, but if you use a wrapper because you're a wangblowsfag, it will default to your account name and shit.

it's always funny how this board pretends to be intellectuals and then you have threads with people who can't even wrap their head about git lol.

>>109013966
>I have no clue why anyone would ever want to put up with all this physical and mental pain
Can you think of a better way of doing things?
In practice the only commands you use will be add and commit, and GUIs for git exists.
>because nobody will hire me otherwise
Nobody would hire you either way.

>>109014081
Politics is very strong in software as society is dependent on technology. This board might aswell be a /pol2/, a lot of the hottest topics on this board are part of a larger battle between different communities, corporations and organizations.

If you can't handle git maybe you're retarded?

It's literally that easy I have never needed anything advanced in git. Just branch off master do your changes, commit you changes rebase on master if your branch is out of date raise a PR and merge back to main.

>>109015267
Case in point lmao. Classic case of a git add -A retard who thinks he knows git.

File: 1773764065417585.gif (180 KB, 226x224)

180 KB GIF

>>109013966
This is unironically one of the best uses of AI. I never had any CI/CD pipelines on my github projects before Claude could just one-shot it even with complicated dependency chains. Now all my repos are quite fancy.

>>109015279
You're so cute when you try to sound like an adult, timmy!

>>109015298
>>109013966
Wait I just actually read the image and post. You're filtered by basic git commands? Bro.

>>109015270
This site is for adults only. You aren't allowed to browse since you are still in middle school. One day you'll get a job and learn things and be allowed to browse and post here. Until then, go somewhere more your speed, like reddit.

>> "hourse"

Back to whatsapp, pajeet

>>109013966
>get a fresher job
>learn about diff, pull, push and commit
>learn a bit about branch switching and reset
>now just let AI do everything

>>109015296
Nice projection, retard

>>109015347
>he unironically uses git add -A
lmao I can't even

>>109013966
Git is nice when you have to maintain older releases and not go totally insane and since its model is decentralized by default, you aren't beholden to insane shit like svn server locks or coordination other than merge conflicts.
Imo I think jj is closer to what people really need, but like all git killers, it has an uphill battle to fight and still needs to "look" like git for upstream server software.

>>109015317
Sorry to crush your dreams but you're not getting a job in tech. You're in your late 30s and still living in your parent's basement, we require at least 5 years of experience, a degree, a portfolio (on git) and AI for our internship position.
Consider applying to Jack in the Box so you can at least contribute something to society.

>>109015401
Principal engineer, 15 yoe, ex-FAGMAN. Keep crying about it, nocoder.

My VCS is just a script that copies a folder into a different folder and appends the time you did that onto the folder name. Literally has never failed me

>>109015419
And how do you diff between releases? You got a script for that too, tardo? Renanes? You sound unemployed.

>>109015298
>Trusting AI to set up one of the most insecure CIs in the world
Jesus Christ.

>>109014826
>modern svn
Let me guess, you still don't have proper staging? How many partial commits do you do because of how shit svn is?
I can't believe anyone is claiming svn is good. Holy shit.

>>109015437
Ever heard of diff and patch?

>>109015437
>And how do you diff between releases?
WinMerge allows you to diff entire folders.
Other guy's right. All you need is a .bat script to copy your folder to the backup location and winmerge to compare any version against any other version.
Git is a piece of badly designed shit

>>109015437
>unemployed
Found the wagie
For your information, you can easily do file existence and content diffs with various cli tools
>*suckles finnish cock*
Oh, sorry. Forgot you're retarded

>>109015483
And how will diff track renames? git tracks this information.

>>109015497
I take it back, you probably are employed because only the dumbest nigger EEs did shit like you described because they're filtered by vcs.
Stop being fucking retarded. Most you morons can be fine with git add, git commit and moving on.

>>109015501
Different git repos actually use different ways to track renames that are not compatible. Several times if you had actual real pro experience, you would have seen cases where github judged that a rename (as per local git on linux) is actually a delete (so the file just vanishes instead of being readded somewhere semantically).

>>109015501
>git tracks this information
no it doesn't. it only tracks that information if you use their special snowflake commands to rename and delete files. if you drag and drop a file in the file explorer, git doesn't catch it and fucks everything up.
it's honestly pathetic how poorly thought out git is.

>>109015507
>Waaah!
>Just accept extremely complex tools that provide no utility beyond the most simple tool you've already implemented!!!
>If I have to YOU have to!!1!!! *points*
Ouch. Sucks to be you, buddy. Maybe find a different job??

>>109015538
git is simpler than your retarded tooling.

File: git_gargler.png (253 KB, 640x749)

253 KB PNG

>>109015558

>>109015589
(You) have to be the most low IQ poster on /g/ right now. Holy fuck.
Here, I'll spoonfeed you: https://learngitbranching.js.org/
that resource should get you 90% of expert level.

>>109015624
This resource is literally wrong on even the most fundamental concepts. Like I called it very early in the thread, the only people who claim to be git experts don't know the first thing about git. It's hilarious.

>>109015758
>more low IQ cope noises
Post facts or fuck off.

>>109015769
>waah I don't know git please spoonfeed me
This isn't kindergarten. Google it. Or ask an LLM, the clanker is already better than you are (it's terrible).

>>109015511
>n-no it doesn't

mv x y
git add .
git status
  ...
  renamed:      x -> y

dumb nigger.

>>109015789
Thanks for proving you have 0 idea about what git is or does

>>109015802
>being this ass blasted
kek holy shit. take your L like a man and fuck off.

>>109015624
> that website
im raelly really glad i use mercurial instead of that shit holy fuck. git sucks

>>109015802
>Y-YOU HAVE ZERO IDE--
R100 x y

noob. I bet you don't even know what the 100 means.

most unemployed thread of all time holy shit

AI can do some weird shit with git that ends up either saving you big time or wasting your time, and the good models that tend to fuck up less are the slowest

also, git is not hard, at most you're gonna fuck up some branching and states, but most of the time it's just gonna be add cherrypick, logs, etc etc

>>109015855
>uses muh ai
>thinks it's even remotely capable of doing git beyond baby 'solo dev at home' shit
No job detected in this one.

>>109015855
and hunting through reflog sometimes. maybe filter-branch when some dipshit puts binary junk in your repo that blows your git repo up to 10GiB (I have seen this in the real world). lfs is frustrating sometimes, but most remotes that matter also support that as well. I don't like it, but it solves the binaries in git problem that svn tardos always say is their strength.

>>109015809
>>109015823
I rest my case.

>>109013966
>failing to automate it
git is not an automation tool nor it is meant to be automated.

>>109015867
do you have any reading comprehension? I said AI is mediocre and humans are faster at git, with the weird edge cases where parsing through logs can be time consuming or confusing

>>109015885
That's not what you said, but I accept your concessions. You're more likely to be employed than I thought.

>>109015867
>implying AI can't use git.
pretty much all AI is good for is trawling through junk data, like spaghetti gits. what the fuck are you asking the AI to do with a git repo otherwise than try and analyze it?

>>109015904
Imagine you have a repo. git status says no change. Git pull says you're up to date. Git push says you can't do this because you are not up to date.
What do you do?
Feel free to ask the AI. I will only answer by 'yes' or 'no', though.

>>109016000
not that anon but wouldn't a git fetch from origin solve this or am i wrong

>>109016036
No. OK, I'll sometimes give slightly more information.
You do git fetch from origin. You get: "Already up to date" as well.

>>109014050
What else is Felipe from the Philippines going to do to kill time?

>>109013966
Use an IDE. The terminal is for the unemployed as you've just demonstrated

>>109016072
that guy is not answering and my answers amount to stash my changes and do a reset hard to be exactly in sync with upstream. That's the extent of my knowledge with it, after that I'm calling a senior :(

>>109016194
Git reports that there are no changes to stash. You reset --hard origin/main. You do another git fetch for good measure, check git status again and it's all clear. You do git push. Nope, you're still not in sync with upstream apparently.

>>109014050
brain energy optimization function that consists of vocalizing difficulty with learning a new tool in the hope someone else from the tribe makes it go away, because that costs less energy than spending time with something until they stop failing at it. this is exponentially compounded by expectations of instant gratification.
it's just monkey business with no self-awareness.

>>109013966
>1) learn 2 entire languages (git and ssh) in addition to what I already need.
I wouldn't hire you either.
I'd listen to someone who maybe used some source control system other than git, if they had some good reasons (manual copying wouldn't cut it), but "won't learn ssh" gets an immediate NO-HIRE from me, and I'm a relative pushover when it comes to tech interviews.
>>109014063
>For more centralized teams all working in the same product, I agree git has some unnecessary complexity.
thing is though, much of the complexity is easily ignored.
Git's decentralized nature makes it great even for personal, random text file versioning. Say I'm fucking with dosbox configuration for an old game:

cd $GAMEDIR
git init .
echo '*' > .gitignore
echo '!dosbox_game00.conf' >> .gitignore
git add dosbox_game00.conf
git commit -m initial

Now I can see modifications, commit changes, and see the log of commits. So if I fuck up the configs I can just look at the logs and revert the file from a previous commit. Much easier than having a bunch of manual backup files lying all over the directory.

>>109016000
is this some retarded gotcha where the answer is the clone is shallow or some gay shit? retarded question. worst case you do what every jr does, git clone into another fucking branch. you've provided fuck all details and your retarded quiz has nothing to do with my comment. my point is you'd point an AI at a git repo to answer specific git related questions, like confusing merge conflict resolutions to understand why stupid shit is in the repo, where blame stops being helpful.

>>109016682
No special gotcha. No shallow clone or anything like that. The original repo was downloaded by git clone without further special parameterization, there are no submodules and no git-lfs.

>retarded question. worst case you do what every jr does, git clone into another fucking branch. you've provided fuck all details and your retarded quiz has nothing to do with my comment

You have 100% of the information you need to solve this, but only if you know git.
You have very solidly demonstrated you don't know shit about git.

>my point is you'd point an AI at a git repo to answer specific git related questions, like confusing merge conflict resolutions to understand why stupid shit is in the repo
That is literally by far the WORST use of AI for these workflows and the precise way it will make shit up and suggest that you frankenmerge or drop everything.

>>109015872
As a bystander: your case is lost. The ignorance of your bitching is disguised with vehemence. The simple code post exposed you, and you got mad.

>>109014806
Major problem with any discussion of version control is how many different environments and ways of working exist in the software world. One reason git got so popular is because it's fast and flexible and works very well in a wide variety of use cases ranging from simple to extremely complex. But it's not the be-all, end-all of version control and /g/ is full of retards who have absolutely no ability to see beyond the end of their nose and only understand the one specific environment and workflow they use.

>>109016733
Thanks for proving my point once again. Please, keep crying. Your tears are my sustenance.

>>109016733
>One reason git got so popular is because it's fast and flexible and works very well in a wide variety of use cases
this. I moved people off of SVN and people are floored how much less retarded it is. it just works.

>>109016622
ya. at work I use git for versioning configuration files too, so I can answer questions like:
I reconfigured blurple at 8am, tuesday, and also get to peer into what I changed with simple tools like git diff REV, or git show REV -- file if I need the old version for some reason.
real simple stuff. it's basically an every problem is a nail and git is a hammer kind of solution, but sometimes that's all you need.

>>109016789
Kek. Clearly never used svn.
That isn't any of the reasons anyone moved off of that clanky shit to git (even clankier though)

>>109016730
>You have 100% of the information you need to solve this
NTA but I have 100% of the information to conclude that you are a cocksucking attention whore that definitely lacks the balls to post the answer before the thread archives. And no I'm not going to humor you with what I think the answer might be, because you have not earned it.

>>109016836
I have. making partial changes because I can't express basic concepts is insane.
I still don't think you can do complex stagings of changes either. but honestly it's been so long since I used that garbage, probably 10 years now, I can't even remember all the stupid copes I did. I'd imagine SVN fixed shit, but it's still retarded.

>>109016836
also, I remember that the SVN setup was slow and some of the copes done was extensive mirroring, which like all distributed systems, has warts that have to be worked around.
git is purely independent of some shitty apache mod_svn server and whatever r/w mirroring you have.

>>109016891
Yes, they fixed a lot of shit. But that's not the point. Git also got a lot of shit fixed over the years and was unusable at best in the beginning. The reason svn sucked is that centralized workflows were inconvenient at the time, networks were slower and less reliable than now. But nowadays everyone uses git in a centralized style so that obviously makes no difference. The speed and convenience of local commands that git had compared to svn having to do a server roundtrip is just not there yet anymore. Merges were also very painful, but that has obviously improved as well over time and git being forced to autoplay changes without any way to turn that off often breaks shit completely silently which is always hilarious.

>>109016836
Not that guy, but I also moved off SVN and git is far superior for all the relevant use cases. (No videogame assets, no binary files, none of that shit).
The critical issue for me was I needed to run local repositories NFS-mounted parallel filesystems, which sometimes had slow metadata lookup issues. Subversion became so slow under those conditions it was nearly unusable, while git worked just fine.

Incidentally, the environments I worked in rarely used subversion branching. Everyone just did their work in their local repository then committed to the trunk. Sometimes there was a "PR" equivalent where you copy/pasted your diffs into a ticket and you were supposed to wait for peer (or manager) review before committing. Branches would only be used on special occasions for specific major work. (all small teams, 5-10 people). But with git, standard workflow involves creating a new branch for everything. Even before we started using github, the workflows looked a lot more like the "github pull request" model (though we didn't use that term at the time)

>>109013966
Unrelated question. Are you indian?

>>109016970
>But nowadays everyone uses git in a centralized style
no they don't?
I can do something akin to svn bisect without a server.

>>109017085
Larp and cope won't save you.

>>109013966
Just use AI, retard.

>>109017110
huh? I can do everything locally with git. that is my point. just because I have a remote, instead of git formatted email patch series, as a sync-point doesn't change that.

>>109017125
Thanks for proving my point once again.

>>109013993
>Git is not GitHub. You can self-host it if you really want to.
Don't even need to self-host. You can just create a local git repo with 'git init' and get to coding.

>>109017131
w-what?! are you retarded? schizo?

>>109017151
can also have filesystem paths, network shares or ssh + paths as remotes as well.
it's kinda neat.

>>109017195
You can do the same with svn.

>>109017225
But svn is dogshit.

>>109017232
Yes, but so is git.

>>109014050
It’s making more sense why so many software devs are getting laid off

>>109017270
ya. most people in tech are wildly incompetent, money chasing retards. sadly the accessibility of a computer and ability to write software with neigh-zero capital cost is why it's so oversaturated with morons who should be wage slaves working in rebar pits.

For a university course I had to make a Unity game and use Github for version control.

Github Desktop randomly said "cannot connect to repository" and asked if i wanted to reconnect.

clicked yes.

github proceeded to delete my entire repository

>>109017746
Microslop poojeet-quality code.
Fun fact: the git-lfs init sequence can do the same thing to your repo (it can also wipe the whole history and everything). Thankfully it's not like it auto-pushes.

>>109017746
this thread is about git, not GitHub.

>>109017746
What that other anon >>109017868 said, but also unless some github tool literally deleted your entire local repository folder you should always be able to recover through the reflog.
That's actually one of the big advantages of Git vs earlier version tools like SVN. You can end up in shitty broken situations but it's usually possible to recover from them.

>>109014198
>aliases with agents
lol lmao even

>>109014275
Post a better one or shut up, we aren't here to manage your hormonal outbursts.

>>109018283
>baby needs a cheat sheet
>for a software so broken and complicated the only way is to spend a few weeks studying it, then asking a guru for help to find the correct exact version of each invocation to use because all the other ones are footguns or broken

>>109017746
brutal stuff

>>109018296
Damn, what a tranny.

>>109017983
The git-lfs example at >>109017761
actually wipes the reflog as well

>>109018322
Fucking jeetware, man.

>>109015218
>Separate versioning per-file
But you wouldn't use SVN either if you wanted that.

>>109018409
retard

File: tortoisegit-full-menu.jpg (40 KB, 800x694)

40 KB JPG

Install tortoisegit and forget about it. Only thinkertrannies spending time remembering git commands.

>>109019590
tortoisegit is just a shitty frontend over the commandline, it doesn't do anything useful to unfuck or choose the right magical version of a command, in fact it usually chooses the wrong thing except for the simple ones.

>>109013966
>entire languages (git and ssh)
kek, filtered hard

>>109017244
then use jujutsu, its git compatible

>>109014755
>>109015160
>>109015168
>>109015279
>>109015315
>"I think this new "industry standard" that adds a mandatory "0123456789" at the beginning of every phone number is pretty retarded."
>"LMAO imagine getting filtered by typing a simple ascending string of numbers!"
OP here. I am perfectly capable of using git.
Just because git is "easy" that doesn't make it any less annoying.
Just because I'm not willing to do waste my time doing meaningless tasks that doesn't mean I'm getting "filtered" by them. It just means I value my time.

>>109013966
>For years I've been working on various kind of stuff and I've never had the slightest need for it.
In other words you've only created 1 man toy projects, thanks for clearing that up

>>109014050
Are you familiar with soft propaganda? This is "ai" agitprop in the form of soft propaganda.