What do I need to know so that I can fairly write git on my resume?

Question

git

What I can do with git:

• Clone a repository or create your own
  
• Commit
  
• Revert the last commit
  
• Load changes from a published repository
  
• push
  
• Create, modify and delete branches
  
• Do a branch merge
  
• Switch between branches
  

What else do I need to know so that I can legally say that I can work with git?

Answer 1

It's enough.
But I highly recommend sticking to Git Flow.
Here in simple language and in Russian:
https://proglib.io/p/git-github-gitflow/

Answer 2

rebase, at what point is it better to do it when merging into the master?
whether it is possible to do push --force in the master?
Interactive rebase why is it needed?
Reset when and what?
https://git-scm.com/book/ru/v2

Answer 3

To the above, add
* just to navigate the terminology - to know how branch differs from tag, what HEAD, STASH are, what pull and fetch do.
* be able to set up your git profile (register a user, register an email)
* Be able to set up authorization - ssh keys to work on the ssh protocol, or be able to save a password to work on the https protocol (you can practice on github).
* be able to view the commit log and navigate it

Answer 4

Of the skills - resolve conflicts.
In general, it is necessary not only to be able, but to understand why and why this is being done.

Answer 5

if you are not sure, write:
- I am familiar with git
- I have skills in working with git
ps maybe later, you will understand that there is already a tiger in git ... but then the question was answered

Answer 6

Git is an everyday tool. Well, if you use it without noticing it. You think to start a task and start a new branch, rather than sticking it into the monitor, remembering how to squabble in git. Rare things, like git bisect, you need to be able to do with Google under your arm. That seems to be for an ordinary developer and that's it.

Answer 7

different teams have a different approach, starting from the description of commits, branches and ending with the fact that everything in 1 branch
IMO needs to be able to
- merge and upload changes
- resolve conflicts
... the rest is a matter of practice, as it learns twice

Answer 8

Every beginner git'er should know about the command git reflog, because if something is broken, then reflog will always save! :)