superbil (@superbil@g0v.social)
find . -not -path './.git/*' | git check-ignore --stdin
用這個指令可以找出 git 底下被 ignore 的檔案清單，用 find 加上一些要或不要的條件之後，再把清單丟給 rsync ，就可以拿來當作不同電腦間的 git 檔案同步了耶
Show Original Post
mahadevank (@mahadevank@mastodon.social)
Nice doc on the internals of Git, helped me understand how it works better.
Its pretty nice how the .git folder is neatly organized and most of the stuff in there is pretty simple and straightforward
Repo for attribution: https://github.com/pluralsight/git-internals-pdf
Direct link to doc: https://raw.githubusercontent.com/pluralsight/git-internals-pdf/master/drafts/peepcode-git.pdf
Show Original Post
tugatech (@tugatech@masto.pt)
JetBrains liberta o DataGrip: popular IDE de bases de dados agora é gratuito para uso não-comercial
🔗 https://tugatech.com.pt/t72197-jetbrains-liberta-o-datagrip-popular-ide-de-bases-de-dados-agora-e-gratuito-para-uso-nao-comercial
#blog #consola #git #ia #IDE #JetBrains #Privacidade #prompts #sem #software #sql #tutoriais
Show Original Post
agowa338 (@agowa338@chaos.social)
Anyone already attempted to do some kind of protocol spoofing or similar to get the "smart" protocol of git's http-protocol to work using static content?
All of the "TODO: document this further." within the docs also do not really help evaluating this 😅
https://git-scm.com/docs/http-protocol
Show Original Post
stsp (@stsp@bsd.network)
I have uploaded the slide set used during my #EuroBSDCon talk about @gothub
https://www.openbsd.org/papers/eurobsdcon2025-stsp-gothub.pdf
https://events.eurobsdcon.org/2025/speaker/WATRDV/
#OpenBSD #Git #GameOfTrees #Hosting
Show Original Post
gothub (@gothub@exquisite.social)
As an alternative to signing up via email, you can use our entropy-powered chat bot (not an LLM) which hands out a limited amount of one-time-use unique payment links which can be used to book a subscription:
ssh signup@gothub.org
Host key: SHA256:SlhsNLc4ZtasXKUmJeUqHHhUdGttyz+NvnfbhJ1VHnY (ED25519)
Before connecting to this bot you may want to get an overview which tiers we currently provide and which features we are planning to add in the long term. Visit https://gothub.org/ for more information.
The links are unique and the amount of links available corresponds to hosting resources we have ready to go without renting more servers. So if you obtain a link then please do use it yourself to book a tier or have someone else do so.
In case the costs seem prohibitive, we should point out that sharing the costs of a #Git hosting space between friends is explicitly allowed by our terms of service. Our goal is not to charge everyone as much as possible but to cover the costs created by renting servers and support some of the hours we spend every week writing free software in-between hours spent doing regular jobs and having a life.
Show Original Post
mhneifer (@mhneifer@mastodon.social)
"Jujutsu fordert Git heraus, ohne Branches und mit Mega-Merges. In dieser Podcastfolge erklärt Daniel Danner, was jj ausmacht und wie es mit Git kompatibel ist."
Show Original Post
slink (@slink@fosstodon.org)
@kly in short, i do not want to work but with a linear history in the main branch. i've seen the mess which inevitably happens otherwise, where with sufficient branching and merging no-one can answer the question any more who did what and when.
(exceptions to the rule are always implied)
2/2 #git
Show Original Post
slink (@slink@fosstodon.org)
@kly @kly i agree and disagree:
moving tags and mega commits are a bad idea.
but a linear history with clear, understandable (on a human scale) individual commits is a very, very good idea. i would think you gave the right reasons, but it seems you came to a different conclusion?
in my experience, the "rebase -i" workflow can mean some extra effort, but usually it is very much worthwhile, for reviewers, git bisect, and regression hunt in general.
1/2 #git
Show Original Post
kdab (@kdab@techhub.social)
Prefer reading over watching? In this blog post, Nicolas dives deeper into managing multiple Git branches without switching. Using --rebase-merges and --update-refs, he shows how to keep history clean, branches in sync, and reviews efficient - all with built-in Git tools: https://www.kdab.com/working-on-multiple-git-branches-without-switching/
#Git #DevTools #CodeReview
Show Original Post
dewomser (@dewomser@social.tchncs.de)
#Linux #Git #Bash
Nach einem Jahr mach ich mal wieder #Datensicherung (Clone nach Hause) aller meiner Github Gists
Es ist diesmal ein 2-Zeiler:
die ersten hundert,
und dann die zweiten
https://gist.github.com/dewomser/6754e38a5eeda3fe0ae7cf611512350f
Show Original Post
dolibarr (@dolibarr@pouet.chapril.org)
We have a new developper in the Team !
The DoliBear is now responsible to assign Pull Request on maintenance branch (v18) to the maintenance team.
Show Original Post