lascapi (@lascapi@social.tchncs.de)
@Sascha the real example a know is :
As a student you got some cloud by the university. You use it to store your project.
Then you learn #git, and you start to use it locally (and synchronised with your cloud) + you have a lot of big files / data in your repo and in some other place on your cloud with hard links in your code.
Then you share your project with some colleges through the cloud, with a lot a data / artefact / database / picture / ... And it becomes virtually impossible as junior dev to find a way to switch every thing to a git forge with all this dependencies all over your hard drive / cloud.
Show Original Post
robertpi (@robertpi@functional.cafe)
Going to self-host a git server for a few projects. Looking for something lightweight and secure.
Any suggestions?
Show Original Post
exa (@exa@mastodon.online)
For the next project that I need to get public on #git (research software) while avoiding slophub and sloplab as much as I can, I shall go with:
Show Original Post
riaschissl (@riaschissl@sigmoid.social)
I’ve been using #Forgejo as a #Git repo server for a few days now for some of my personal & PhD projects and experiments.
And what can I say: I’m thrilled! I’m very familiar with #gitlab, but Forgejo has nothing to fear from the comparison! Of course, there's no feature parity, but it seems Forgejo/Gitea have simply focused on the essential aspects, and that works perfectly. Excellent performance, low resource footage, good CI/CD. On top of that, it’s fully FOSS, no ifs or buts!
Show Original Post
habr (@habr@zhub.link)
Как мы потеряли GitBook за 5 минут и нашли Gramax — open-source альтернативу, которую теперь используем сами
Один клик — и ваша документация может исчезнуть. Именно так и произошло с нами. Поэтому мы нашли open-source альтернативу, где данными владеем только мы — и никакой регион это не изменит.
https://habr.com/ru/articles/1019230/
#Gramax #GitBook #open_source #документация #docsascode #Markdown #Git #стартап #альтернатива_GitBook #командная_документация
Show Original Post
orhun (@orhun@fosstodon.org)
Found an amazing tool for fixing broken Git history 💯
⏪ **git-time-machine** — A TUI for navigating Git reflog
🔥 Rebase, reset, undo any Git mistake quickly with a visual timeline
🦀 Written in Rust & built with @ratatui_rs
⭐ GitHub: https://github.com/dinakars777/git-time-machine
#rustlang #ratatui #tui #git #history #vcs #devtools #productivity #terminal
Show Original Post
n (@n@gotosocial.tourmentine.com)
[lien] Git Isn’t Just for Developers. It Might Be the Best Writing Tool Ever #gik #git #bks #txt
Show Original Post
qiita (@qiita@rss-mstdn.studiofreesia.com)
はじめての Git 実務ガイド：ブランチ運用からトラブル対処まで
https://qiita.com/hiroki_notes/items/6358c8f99b66baba8655?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #Git #rebase #branch #pull #ブランチ
Show Original Post
andrii_sudak (@andrii_sudak@infosec.exchange)
Stop the Stash-Pop Panic! Why Git Worktree is my IaaS Game Changer.
Have you ever been deep into a complex feature branch, and suddenly… BOOM. A critical bug in main or production needs your immediate attention.
You reach for git stash. You pray you won't forget where you were. You switch. You fix. You stash pop… and then the anxiety hits. Wait, which stash was that? Did I just overwrite my local terraform state?
For me, this was the ultimate flow-killer. Until I integrated Git Worktree into my workflow.
The Problem with the "Standard" Way:
As an IaaS specialist, my changes aren't just code, they represent infrastructure states. Standard branching meant:
* git stash my complex IaaS changes.
* git checkout main and wait for the local environment to sync.
* Fix the bug, deploy, and verify.
* git checkout feature and wait again.
* git stash pop and spend 15 minutes regaining focus.
The Solution: Git Worktree
Git Worktree allows you to have multiple checkouts of the same repository in different directories simultaneously. It’s a game manager.
Instead of switching branches in one folder, I simply add a new worktree:
git worktree add ../hotfix-folder main
* Zero Context Switching: My feature branch remains open and untouched in its own folder.
* Instant Parallelism: I can run a long Terraform plan in one worktree while fixing a bug in another.
* No Stash Chaos: No more "which stash is which?" or accidental data loss.
The PyCharm Factor:
I’m a dedicated PyCharm fan. I love its built-in Shelf tools for quick code shifts. But for IaaS, where context is everything, Worktree takes it to the next level. It’s not about replacing PyCharm’s tools, it’s about giving your IDE multiple entry points into the same project state.
The Takeaway:
A worktree is essentially a branch that lives in its own directory. It’s the fastest way to handle "urgent" tasks without losing your "deep work" momentum. If you’re tired of the stash/pop dance, this is your sign to switch.
#git #gitworktree #iaas #infrastructureascode #pycharm #devops #productivity #workflow #softwareengineering #cloudinfrastructure
Show Original Post
somebitslinks (@somebitslinks@tech.lgbt)
Jujutsu Tutorial: Overview of the new version control system that can replace git
https://steveklabnik.github.io/jujutsu-tutorial/
#versioncontrol #programming #vcs #git #jj #+
Show Original Post
lxrs (@lxrs@mastodon.online)
I just discovered that there’s a #Forgejo client for #iOS, named #Forji. https://codeberg.org/secana/Forji https://apps.apple.com/de/app/forji/id6759843639?l=en-GB
Show Original Post
anniwherebuthere (@anniwherebuthere@mastodon.social)
I have an unhealthy relationship with #git: It’s always push & pull :(
Show Original Post