Added git lock rule

[tobibechtold]

No description provided.

[tobibechtold]

My colleague and i just ran into a funny situation while pair programming and trying to bring an out of date branch up to date with the master. We weren't quite sure what actually has changed and he said "just type git log". And so i typed "git lock". He said no... log with a "g". So i said: " no problem, i got this" and typed "fuck". But instead of "log" fuck was suggesting "lsck". So this is the intent of this PR.

[scorphus]

That's a nice story! There's always some good outcome of pair programming. If only Git would list log as one of the most similar commands then your friend would be amazed 😄

As you probably know, there's already a git_not_command rule. I'd recommend changing it instead, in a way to include the most common typos. Something like having a dict like this:

COMMON_TYPOS = {
    'copy': ['branch'],
    'list': ['branch'],
    'lock': ['log'],
    'switch': ['checkout'],
    'update': ['fetch', 'fetch --all', 'fetch --all --tags', 'remote update'],
}

And then in get_new_command:

    # ...
    matched = [replace_argument(command.script, broken_cmd, common_typo)
               for common_typo in COMMON_TYPOS.get(broken_cmd, [])]
    # ...
    matched.extend(...)  # add Git's similar commands to the end of the list
    # ...

What do you think?

[tobibechtold]

Hey that sounds like an even better idea. I will try to tackle this next week. Thank you :)

[scorphus]

Hey, @tobibechtold! Hopefully you're willing to have anoother look at this PR!

[preetham1239]

Hello @scorphus

I'm new to open source and I am interested in contributing to thefuck. Can I work on this issue?

[scorphus]

Go for it, @preetham1239 😊

[preetham1239]

Hello @scorphus, I made a pull request #1429, please let me know if I need to make any changes as this is my first one.