portturk.blogg.se

1. #Thefuck terminal plugin update#
2. #Thefuck terminal plugin Patch#
3. #Thefuck terminal plugin code#
4. #Thefuck terminal plugin series#

Remember the complicated information model in step 1? It keeps growing, like a cancer.

#Thefuck terminal plugin series#

Translation: git-rebase – Sequentially regenerate a series of commits so they can be applied directly to the head node 4. Git-rebase – Forward-port local commits to the updated upstream head Here’s a description for humans: git-push – Upload changes from your local repository into a remote repository

#Thefuck terminal plugin update#

Git-push – Update remote refs along with associated objects They describe the commands from the perspective of a computer scientist, not a user. The man pages are one almighty “fuck you”.

#Thefuck terminal plugin Patch#

It combines email reading with patch applying, and thus uses a different patch syntax (specifically, one with email headers at the top). The most spectacular example of this is the command “git am”, which as far as I can tell, is something Linus hacked up and forced into the main codebase to solve a problem he was having one night. The various options of “git reset” do completely different things. Specifying filenames completely changes the semantics of some commands (“git commit” ignores local, unstaged changes in foo.txt “git commit foo.txt” doesn’t). But the shortcut for “git branch” combined with “git checkout”? “git checkout -b”. Some “shortcuts” are graced with top level commands: “git pull” is exactly equivalent to “git fetch” followed by “git merge”. The command line syntax is completely arbitrary and inconsistent. Now Git: you have files, a working tree, an index, a local repository, a remote repository, remotes (pointers to remote repositories), commits, treeishes (pointers to commits), branches, a stash… and you need to know all of it. In fact, branches are tags, and files you already know about, so you really need to learn three new things.

That’s pretty much everything you need to know. As a point of reference, consider Subversion: you have files, a working directory, a repository, versions, branches, and tags. The information model is complicated – and you need to know all of it. What a pity that it’s so hard to learn, has such an unpleasant command line interface, and treats its users with such utter contempt. It has a powerful distributed model which allows advanced users to do tricky things with branches, and rewriting history.

#Thefuck terminal plugin code#

Also dont use with command that contains sensitive information like security tokens etc.Git is the source code version control system that is rapidly becoming the standard for open source projects. Please note: dont use it with any commands that’s destructive because it would rerun the command. Also open to see if anyone has idea to improve the prompt or how it works. So of you can try it out when you face errors and share how helpful its solution is. I am looking to see if anyone find it helpful since I have been using it lightly and only when I hit errors. So my CLI does fetch the last command run, rerun it and fetch the stderr to be feed into ChatGPT for help.

I took some inspiration from this( ) CLI tool I was introduced some years ago, which helps fix common errors in your cli command like misstype or need sudo. I feel making ChatGPT to be the initial debugger to guide whats the error means and what should I look for to fix this error. Many hours passed and I usually gets frustrated. Sometimes the error might have many different reasons and search results shows many solutions. Its hard searching for answer for this kind of errors in SO or google. But there are time I face errors I never seen before. If we are familiar with what we are doing, fixing command line errors is straightforward. When you hit an error on your command line, get immidiate help and fix from ChatGPT.

I built this CLI tool to fix command line errors with ChatGPT.