What Git experience does a web developer need to work on a team in a company?

Question

git

I have little experience with VCS - I am the only front-end and back-end developer at my first office job, I just commit our project through the Git GUI and sometimes upload it as a backup to BitBucket using SourceTree . What level of Git work is typically required (in detail)? Who works in teams? Should I learn linux console commands for Git or do they usually work through clients? What do you need to be able to do in this regard?

Answer 1

It is advisable to understand what they do and why the following commands are needed:

git status
git checkout
git reset
git fetch
git pull
git push
git diff
git add
git commit
git stash

Answer 2

as I usually do:
1) create a new branch with my feature (and you will automatically switch to it):
2) do what I need
3) commit

git add -A
git commit -m "Name commit"
git push origin name-branch

4) Update my branch with respect to master (so your last commit will be on top)
5) Go back to the correct branch (master or developer)
6) Update my local branch
7) Merge changes and push

git merge name-branch
git push origin master

Answer 3

Enough
git push
git pull
git commit
git add

Answer 4

Get rid of GitGUI and go to the console in your projects, that should be enough.

Answer 5

I asked about git at interviews only to understand the general development. This is not a recruitment criterion. An adequate candidate will spend no more than a week on mastering the Git.
Git commands may not know at all. It is enough to work with some version control system.
Unless of course this is a DevOps specialist)

Answer 6

Fifteen Minute .

Answer 7

None unless you are an architect who urgently needs to decide which VCS to use

Answer 8

There are basic commands. They are listed above.
You can also work through the GUI, but still understand which command is being called.
And there is a development flow. It's not bad to understand him either.
Here is an old, but not outdated article https://habrahabr.ru/post/106912/
And when you join the development stream, you start not by writing code, but by switching to the desired branch or by adding a new one. You make commits after each small but logical edit.