FAQ Portal
Categories
Search
About
Contacts
UK
RU
EN
Home
Technology
Programming
Git
Git
100 questions
How to undo a commit?
•
reset --soft HEAD~
1.
•
reset --hard HEAD~
1.
•
revert HEAD.
•
commit --amend.
How to resolve a conflict?
•
git status.
•
Find markers.
•
Edit.
•
git add.
•
git commit.
merge vs rebase?
•
merge — merge commit.
•
rebase — linear history.
•
merge preserves history.
•
Do not rebase public branches.
How to work with branches?
•
git branch.
•
git checkout.
•
git checkout -b.
•
git branch -d.
•
git merge.
What is stash?
•
Saving changes.
•
git stash.
•
git stash list.
•
git stash pop.
•
git stash apply.
Git: how to configure .gitignore and what to add?
Start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to write good commit messages and structure history?
Practice for «Git»: write a test/check that breaks, then fix the code. This way you don’t «treat symptoms».
Git: how to work with remote/origin and multiple repositories?
Answer about "Git": read the documentation and errors completely. The error message almost always indicates what is wrong.
Git: how to safely revert changes in team collaboration?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: question №10
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to configure .gitignore and what to add to it?
For "Git": keep the code simple: small functions, understandable names, one level of abstraction. This reduces the number of bugs.
Git: how to write good commit messages and format history?
On the topic of "Git": start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to work with remote/origin and multiple repositories?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to safely revert changes in team collaboration?
Answer about "Git": read the documentation and errors completely. The error message almost always indicates what is wrong.
Git: question №15
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to configure .gitignore and what to add to it?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to write good commit messages and format history?
For "Git": keep the code simple: small functions, understandable names, one level of abstraction. This reduces the number of bugs.
Git: how to work with remote/origin and multiple repositories?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half the debugging.
Git: how to safely revert changes in team collaboration?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: question №20
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to set up .gitignore and what to add there?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to write good commit messages and structure the history?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to work with remote/origin and multiple repositories?
On "Git": keep the code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to safely revert changes in team collaboration?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half the debugging.
Git: question №25
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: how to set up .gitignore and what to add there?
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to write good commit messages and structure the history?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to work with remote/origin and multiple repositories?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to safely revert changes in team work?
Keep your code simple for "Git": small functions, clear names, one level of abstraction. This reduces bugs.
Git: question №30
On the topic of "Git", start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to set up .gitignore and what to add there?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to write good commit messages and format history?
Answer about "Git": read the documentation and errors completely. An error message almost always indicates what is wrong.
Git: how to work with remote/origin and multiple repositories?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to safely revert changes in team work?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: question №35
For "Git", keep the code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to set up .gitignore and what to add there?
On the topic of "Git", start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to write good commit messages and format history?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to work with remote/origin and multiple repositories?
Answer about «Git»: read the documentation and errors thoroughly. The error message almost always indicates what is wrong.
Git: how to safely revert changes in team collaboration?
For «Git»: logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: question №40
If the question is about «Git», start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to configure .gitignore and what to add there?
With «Git», keep the code simple: small functions, understandable names, one level of abstraction. This reduces bugs.
Git: how to write good commit messages and structure history?
On the topic of «Git», start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to work with remote/origin and multiple repositories?
Practice for «Git»: write a test/check that breaks, then fix the code. This way you don't «treat symptoms».
Git: how to safely revert changes in team collaboration?
Answer about «Git»: read the documentation and errors thoroughly. The error message almost always indicates what is wrong.
Git: question №45
For «Git»: logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to configure .gitignore and what to add there?
If the question is about «Git», start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to write good commit messages and structure history?
With «Git», keep the code simple: small functions, understandable names, one level of abstraction. This reduces bugs.
Git: how to work with remote/origin and multiple repositories?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half of debugging.
Git: how to safely revert changes in a team setting?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: question #50
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to set up .gitignore and what to add there?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to write good commit messages and structure history?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to work with remote/origin and multiple repositories?
On "Git": keep your code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to safely revert changes in a team setting?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half of debugging.
Git: question #55
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: how to set up .gitignore and what to add there?
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to write good commit messages and structure history?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to work with remote/origin and multiple repositories?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to safely revert changes in team work?
Keep your code simple with "Git": small functions, clear names, one level of abstraction. This reduces bugs.
Git: question №60
For "Git", start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to set up .gitignore and what to add there?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: how to write good commit messages and organize history?
Answer about "Git": read the documentation and errors thoroughly. Error messages almost always tell you what is wrong.
Git: how to work with remote/origin and multiple repositories?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to safely revert changes in team work?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: question №65
For "Git", keep the code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to set up .gitignore and what to add there?
For "Git", start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to write good commit messages and organize history?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat the symptoms".
Git: how to work with remote/origin and multiple repositories?
Answer about "Git": read the documentation and errors completely. The error message almost always indicates what is wrong.
Git: how to safely revert changes in team collaboration?
For "Git" it is useful: logging, profiling, and working with metrics. Optimization without measurements is guesswork.
Git: question №70
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to configure .gitignore and what to add there?
For "Git" keep the code simple: small functions, understandable names, one level of abstraction. This reduces the number of bugs.
Git: how to write good commit messages and format history?
On the topic of "Git" start with reproducibility: minimal example, version, steps. This is half of debugging.
Git: how to work with remote/origin and multiple repositories?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to safely revert changes in team collaboration?
Answer about "Git": read the documentation and errors completely. The error message almost always indicates what is wrong.
Git: question №75
For "Git" it is useful: logging, profiling, and working with metrics. Optimization without measurements is guesswork.
Git: how to configure .gitignore and what to add there?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to write good commit messages and format history?
On the topic of "Git" keep the code simple: small functions, understandable names, one level of abstraction. This reduces the number of bugs.
Git: how to work with remote/origin and multiple repositories?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half of debugging.
Git: how to safely revert changes in team collaboration?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: question №80
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to set up .gitignore and what to add there?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to write good commit messages and structure history?
If the question is about "Git", start with simple causes: data types, null/undefined, dependencies, environment, access rights.
Git: how to work with remote/origin and multiple repositories?
On "Git": keep the code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to safely revert changes in team collaboration?
On the topic of "Git": start with reproducibility: a minimal example, version, steps. That's half of debugging.
Git: question №85
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to set up .gitignore and what to add there?
Answer on "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to write good commit messages and structure history?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to work with remote/origin and multiple repositories?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: how to safely revert changes in team work?
Keep your code simple for "Git": small functions, clear names, one level of abstraction. This reduces bugs.
Git: question №90
Regarding "Git": start with reproducibility: minimal example, version, steps. That's half of debugging.
Git: how to set up .gitignore and what to add there?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to write good commit messages and format history?
Answer about "Git": read the documentation and errors thoroughly. An error message almost always indicates what is wrong.
Git: how to work with remote/origin and multiple repositories?
For "Git": logging, profiling, and working with metrics are useful. Optimization without measurements is guesswork.
Git: how to safely revert changes in team work?
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.
Git: question №95
For "Git": keep your code simple: small functions, clear names, one level of abstraction. This reduces bugs.
Git: how to set up .gitignore and what to add there?
Regarding "Git": start with reproducibility: minimal example, version, steps. That's half of debugging.
Git: how to write good commit messages and format history?
Practice for "Git": write a test/check that breaks, then fix the code. This way you don't "treat symptoms".
Git: how to work with remote/origin and multiple repositories?
Answer on "Git": read the documentation and errors in full. The error message almost always indicates what is wrong.
Git: how to safely rollback changes in team work?
For "Git" it is useful: logging, profiling, and working with metrics. Optimization without measurements is guesswork.
Git: question №100
If the question is about "Git", start with simple reasons: data types, null/undefined, dependencies, environment, access rights.