Neat tutorial, I think I've to try #jujutsu out now!
https://www.stavros.io/posts/switch-to-jujutsu-already-a-tutorial/
New blog: a clean guide to using git worktrees to work on parallel branches without stashing or temp commits.
https://blogs.dgplug.org/sandeepk/git-worktree
TIL that `git add` has a `--edit` (or `-e`) option that allows you to edit the patch to be applied, i. e. to remove changes that you don't want to add. This is really helpful for me as I have a tendency to change more than one thing at a time, but I still want each of my commits to contain one change only.
The Future of AWS CodeCommit, by @awscloud.bsky.social:
https://aws.amazon.com/blogs/devops/aws-codecommit-returns-to-general-availability/
Los comandos que necesito para trabajar con git desde la terminal https://myblog.clonbg.es/los-comandos-que-necesito-para-trabajar-con-git-desde-la-terminal/ #Terminal #Git https://clonbg.es

My friend Jim @jammcq and I were discussing #precommit (used with #Git). The typical case is simple but annoying:
* You’ve staged all the needed files for commit (with `git add`)
* You attempt the commit
* Trailing whitespace (in this example) makes `pre-commit` deny the commit
* No commit actually happened. Everything in the staging area is untouched. Code in your working copy has been changed to fix the problem.
* Those fixes must now be staged (another call to `add`)
* You must re-run the commit
Sure, the up-arrow helps, but still.
Here’s another way:
* You happen to be working on the file `foo.py`; but you haven’t staged anything yet. You’re just editing away
* Let’s fix some whitespace problems: `pre-commit run trailing-whitespace --files foo.py`
* `foo.py` is modified in-place, now `add` and `commit`
* Shorten the long `pre-commit` command with an alias; you control the exact conditions to look for and fix
Is it better? Well … it’s different. It’s better in some ways. It might be a better fit for the way you personally work.
I have a #git #worktree question for the masses. What is the best way to handle core configuration for a project when a new worktree is added? For example, in a Rails project, when creating a worktree I then need to copy over the application.development.yml and the database.yml to be able to do anything with the code.
Is there a best practice to follow? #AskMastodon
I just updated a lot of stuff on my GitHub and added community stuff. Feel free to check it out! :) https://github.com/Maingron
#github #opensource #maintenance #webdev #contributing #codeofconduct #foss #oss #floss #html #css #javascript #git
For those who know or have mastered Git (to some extent):
I'm looking for a way to download a single folder from a Git project.
The solution should work with any Git forge and should not be limited to GitHub 🙂
Here's a solution I came up with. It's not perfect since it downloads the entire .git folder, which can be quite large depending on the project:
```shell
git clone --no-checkout https://path/to/my/repo.git .
git sparse-checkout set my-folder
git checkout HEAD -- my-folder
rm -rf .git
```
Does anyone have any other ideas on how to achieve this more efficiently?
Thanks 🙇
【AWS】DevTools布教活動CodeCommit編【アドカレ2025】
https://qiita.com/Nana_777/items/a8be2eee9ee9d81326cb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #Git #AWS #DevTools #CodeCommit #TopEngineers
*Absent-mindedly copies the commit message from the Sublime Merge GUI into the terminal*
git commit -m "Remove BASENAME config, add `history` as non-transitive dep"
*presses Return*
Oh. 😦 Ohhh. 😧 Oh okay makes sense 😂
#git #puttering #BlackSwanEvent
Und ewig grüßt das Murmeltier ... auch diese Woche wieder Updates für GitLab, die man eingespielt haben sollte. Es gibt zwei Updates mit dem Bedrohungsgrad „hoch“.
Kann man sich inzwischen fast einen Wöchentlichen Reminder für stellen. Kommt fast jede oder jede zweite Woche was. Gute das die dann immer sehr gut automatisiert reinlaufen und nicht viel Arbeit machen.
https://social.heise.de/@heisec/115626324825542738
https://about.gitlab.com/releases/2025/11/26/patch-release-gitlab-18-6-1-released/
#gitlab #updates #sicherheitsupdates #git
