Git для новичков: ветки, коммиты и первый pull request
Git — это вызов, через который проходит каждый второй новичок в разработке. Ветки называются «asdasd», коммиты — «правки», а pull request пугает своей красной кнопкой. Знакомо? Меня зовут Сергей Прощаев, я Tech Lead в FinTech и преподаватель на курсах в OTUS. В этой статье разбираем самое главное: как создавать ветки и почему их нельзя называть как попало, что писать в коммитах, как сделать pull request в лучших практиках команд разработки Разобраться в Git
https://habr.com/ru/companies/otus/articles/994162/
#java #Git #version_control #ветки #коммиты #pull_request #туториал #автоматизация_тестирования #Java_QA
https://blog.jonudell.net/2026/03/12/how-llms-make-git-and-github-easy-to-use-and-learn/ #git #github #learning
Nothing requires us to cede autonomy to our freakishly talented LLM assistants. We direct their efforts, and they learn from us. As we do the work they wield tools on our behalf. We can, if we choose, learn from them how best to use those tools, even as we often delegate the use to them.
https://blog.jonudell.net/2026/03/12/how-llms-make-git-and-github-easy-to-use-and-learn/
"How do you know when someone uses Linux? Oh don't worry, they'll tell you." goes the old joke.
I just found "I use arch btw" as a git commit author name in a PR I'm reviewing.
Using different git configurations without manual steps. Like for work and private.
https://tjvb.nl/posts/multiple-git-configurations?rel=mastodon
Sooo...
Since nobody has been complaining about suuuper long commit messages resulting from repeated cycles of review-changes-squashing, I have started sneaking in little bits of ASCII-art at the lower ends of the Very Long commit message.
Since nobody ever really reads those, I think they will go undiscovered ...for ever.
But still, I'll know they're there.
Updated Jujutsu to 0.39.0 for #guix. In this PR, or anyone that wants to try it:
https://codeberg.org/guix/guix/pulls/7078
Nice features are a new `jj arrange` which is kinda `git interactive rebase` but without the fear.
And, `jj bookmark advance` which makes it easy to move a bookmark (branch) forward. Improves interacting with Git branches.
Закончил эпопею с переносом реп на малинку под #git.
Некоторые конфиги хранились под #fossil, в частности тот же используемый vimrc.d и zshrc.d, казалось, сложные и нервные, и используемые, которые не хотелось бы потерять вместе с историей.
Но через `fossil git export` было сделано без проблем. Сначала несколько реп через временный каталог переместил, но оказалось, что есть волшебная опция `autopush` с помощью которой уже по списку поперезаливал. Ну, ок.
#heptapod 18.7.6 released, bumping #gitlab to the 18.7.6 regular patch/security version.
Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.7.6/HEPTAPOD_CHANGELOG.md
Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
The Staging Area is great... but what if you could just safely skip it? 🤔
Sometimes you just want to grab a few files and say "Commit these." In the #CLI, this leads to the tedious git add file1 file2... typing exercise 😅
#SmartGit handles this for you:
✅ Select multiple files? It commits what you highlighted. No manual staging required.
✅ Select just one file (when you have others modified)? It asks: "Did you mean this selected file or all of them?
Let's settle this in the poll👇

#heptapod 18.8.2 released, bumping #gitlab to the 18.8.6 regular patch/security version
Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.8.2/HEPTAPOD_CHANGELOG.md
Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
I’m missing something. Anyone using git-crypt with git worktrees? I keep getting smudging errors when I try to unlock it. Any tips? #git #gitcrypt