I had a collage who kept linux commands like ls -l, ssh and git commit/pull/push in .txt file and when he needed to use them, he just copy from the file and paste them to command line EVERY F*CKING TIME. He just didn't won't to learn them.

There's a way to make him learn: replace a few commands with "rm -rf /" and wait.

All hail `alias`!

Didn't even want to make it a bash script?

I could understand him doing that but a text file... Really...

How long has he been using Linux?

Maybe he's dyslexic and that's quicker than making sure he spelt everything correctly?

Personally, I don't have all the commands I need memorized, but I know it's possible. I used to struggle with pushing projects to GitHub, but I learned three things:

git add . (people hate me for this, I don't care, I'm not gonna type the fucking names of files I modded if I don't have to. Yeah, I'm not gonna be surprised when someone here comes at me - just know it doesn't change things for me when you do)

git commit -m "Commit message here"

git push origin branch-name-here

Branch creation I think is "git checkout -b new-branch"

Listing commits in chronological order IIRC "git log --reverse" (that's a newer one I recently discovered, I could be wrong)

Checking un-committed changes in the staging area: "git status" (another one I recently learned about, IK imma fuckin noob)

However, I will say this: I'm learning more about the git CLI tools. I want to understand more about stuff like branches and merging, and stashing etc. Then, I want to memorize those for when I need them.

And don't forget "git pull <remote repo URL> <branch name>" to pull changes others pushed.

And the obligatory "git branch" so you don't fuck things up workflow-wise.