Real git involves a lot of sweat, requires you to clean up any mess you make, and communicate with any partners about their preferred techniques instead of rawdogging it and waiting for issues. The pushing and pulling will come naturally but you need to know how and when to release, and be clear about how you wish to commit. Nightly is an option but good luck getting everyone on board. People might judge you for using the word "master" but it should be alright in private.

[–] colonelp4nic@lemmy.world 14 points 2 days ago (2 children)

I'm literally a software dev working for a top company and I can barely use git on the CLI. I do all of my version control operations using a GUI, so there's no sense in gatekeeping any of that. This is true of both my work projects and personal ones. It's cool if you prefer the CLI, but it is absolutely not a required skill in order to have a successful and meaningful career.

[–] hex@programming.dev 1 points 1 day ago

It's not even about the CLI. it's about hygiene

[–] mark3748@sh.itjust.works 16 points 2 days ago (1 children)

I agree that the gatekeeping isn’t a good thing, but you should learn at least the basics of the CLI. It will give you a better understanding of what’s going on behind your GUI and makes troubleshooting and fixing problems a lot easier.

Definitely not required but it is absolutely a skill worth having.

[–] Azzu@lemm.ee 6 points 1 day ago

It's absolutely not a skill worth having. If you ever run into issues and need the CLI, you can always get your knowledge right in that moment. If you already can do everything with your GUI and get the same results, getting the knowledge to do it some other way is just wasted time and duplicate work.

[–] BearOfaTime@lemm.ee 7 points 2 days ago (1 children)

People might judge you for using the word "master" but it should be alright in private.

I snorted. It was my inner 12-year-old's fault. (Also because of recently some idiots getting up in arms about these terms in technology.)

[–] Prandom_returns@lemm.ee 1 points 1 day ago* (last edited 1 day ago)

"up in arms":

Reality:
-- "just don't use them, some people find them offensive"
-- "ok"

Anonymous techbros online:
"yOu CanT sAY aNYtHiNg ThEsE daYs"

[–] 4am@lemm.ee 5 points 1 day ago

involves a lot of sweat, requires you to clean up any mess you make, and communicate with any partners about their preferred techniques instead of rawdogging it and waiting for issues. The pushing and pulling will come naturally but you need to know how and when to release, and be clear about how you wish to commit. People might judge you for using the word "master" but it should be alright in private.

Don’t talk about my mom that way

[–] bjorney@lemmy.ca 17 points 2 days ago (2 children)

Git doesn't automatically recursively add all files in the directory to the repository though - VSCode decided that should be the default behavior, while other editors (intellij) ask if you want to add newly created files to version control

[–] hex@programming.dev 1 points 1 day ago* (last edited 1 day ago)

I just hate the vscode source control. It has always felt clunky and like it breaks things (or i just never figured out the workflow - either way i dont need it lol) It is way clearer to see what is happening the console

[–] ApexHunter@lemmy.ml -3 points 1 day ago (1 children)

That's how git works. Every file and subfolder under the repo's root folder belongs to the repo.

[–] bjorney@lemmy.ca 4 points 1 day ago

What does git add xxx do then

[–] Kaeru@slrpnk.net 9 points 2 days ago (2 children)

Alright you convinced me its time to pick up this skill. How does one best learn git? Just play around with it and break things?

[–] LordPassionFruit@lemm.ee 7 points 2 days ago (1 children)

That's basically how I did it.

To properly learn it using this method, create a directory that contains only text files and sub directories and treat it like a real project. Add files, delete them, play around with updating the repository. Try and go back a few updates and see how the things react. Since it's not a real project there's no risk of loss, but you'll still get to see the effects of what you do.

[–] mEEGal@lemmy.world 4 points 2 days ago

that's a necessary step in your learning process, but certainly not sufficient. I'd recommend reading the book, since it shows in greut detail the inner workings of Git along with the basic concepts :

https://git-scm.com/book/en/v2

[–] mEEGal@lemmy.world 5 points 2 days ago

read the official book : https://git-scm.com/book/en/v2