Explore >> Select a destination
|
You are here 
|
www.aaron-gray.com | ||
| | | | |
habr.com
|
|
| | | | | ??? ???????? ? ?????????? ???????? ?? ????? ?????, ??????? ? ????????? ??? ?????????? ??????????, ???????????? ???????? ??? ????, ?? ??????? ?????? ???????. ????????, ??? ???? ????? ??????????... | |
| | | | |
arnorhs.dev
|
|
| | | | | We use git as our versioning tool at work and I've gradually been learning a few tricks on how to speed up my development time and time spent managing my repo. When jumping between branches, continuing your work from where you stopped last time, etc., you very often open the same files as you were editing in a previous commit. This may not be a problem if you use something like Command-T for vim or rely on the file browsing in TextMate, but often it might just be quicker to open all the files from a part... | |
| | | | |
www.erikschierboom.com
|
|
| | | | | Introduction When using git, local branches can track remote branches that no longer exist (the remote branch is gone). To identify these branches, we first have to cleanup (prune) the remote's branches: $ git fetch -p From https://test.com - [deleted] (none) -> origin/disable-feature-x - [deleted] (none) -> origin/fix-typo - [deleted] (none) -> origin/grammar-fix In this case, three remote branches were deleted. Let's see if we have local branches that are tracking deleted branches: | |
| | | | |
blog.risingstack.com
|
|
| | | Let's take a look at the available options & tools to debug Node.js: the pino & debug modules, the built-in debugger, and more. | ||
