social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
#git 2.55.0 from #Debian unstable rebuilds just fine on stable (trixie) without having to backport any build dependency. Hence, if you want to try the new #gitHistory command https://git-scm.com/docs/git-history on stable, you can just `apt source` + `dpkg-buildpackage` and off you go. (You're welcome.)
"Gut Ding will Weile haben"
vs.
"Warum bin ich nicht schon viel früher auf die Idee gekommen?!"
Na jedenfalls: bin jetzt bei github registriert (und codeberg) um mit Jekyll Markdown-Inhalte in HTML-Seiten zu integrieren und als github-pages zu speichern, zum Üben erstmal.
I may or may not be tweaking my own fork of a static site generator for #git repos... 👀
Parce que je vous aime bien, je vous file un tuyau. J'ai testouillé 'ec' comme outil de résolution de conflits. Ça marche pour les conflits #git et #jujutsu, et ça m'évite d'avoir à tout gérer à la main, parce "ours" et "theirs", c'est imbittable et c'est pas le même sens quand c'est merge que quand c'est rebase
En plus y'a la possibilité d'injecter les deux côtés (oui, parfois c'est ce qu'on veut) et au pire tu fais "e" et le fichier s'ouvre dans $EDITOR.
We've released git-carrier, a git extension for working on large merges with many conflicts across the team.
It parks merge conflicts into ordinary commits, so resolution work can be split, handed over and reviewed using a normal git workflow. Three git commands in one script, no dependencies.
Right now, merging Signal in our tree is our bottleneck and delays updates.
git-carrier is one of the tools we're building to fix it.
https://github.com/git-carrier/git-carrier
Open to questions or suggestions. #git
What happens when a decision in your repository exists because of a decision in another repository?
Follow the link.
And then follow the links from there.
That's what the new Keep the Why Globe does: it follows explicit reasoning links across repositories, one hop at a time.
Each repository stays authoritative for its own reasoning. There is no graph database and no central project-memory service.
Git distributes the files. The browser follows the references. The graph appears as a consequence.
https://blog.technopathy.club/the-globe-following-your-reasoning-into-other-people-s-repositories
Git 3.0's upcoming SHA-256 default will be a costly mistake
https://blog.gitbutler.com/git-3-sha-256
@AntoineD Attention, je pars en quenouille : #git.
Mais pas que pour ça.
Dans mon monde merveilleux, ça devrait aussi être utilisé dans tous les morceaux de la vie publique qui impliquent une proposition ou l'altération d'un texte.
La traçabilité à la virgule près de qui à fait quoi comment.
Pour une tribune : t'ajoutes ton nom, tu signes le commit avec ta clé #GPG, et tu pousses.
Bam, libre, gratuit, distribué, vérifiable, auditable.
Keep the Why is now available as a Pi package 🎉
Install it with:
`pi install npm:keep-the-why`
Same open Agent Skill, now directly installable through Pi's package system.
The project rationale stays as Markdown in Git. No database, no daemon, no account, no cloud backend.
Most agent memory adds another database, service or vendor account.
Keep the Why is FOSS and Git-native.
The why behind decisions lives as Markdown in the repository. Git handles versioning, reviews, permissions, forks, merges and distribution.
No database. No daemon. No cloud backend. No second source of truth.
A rejected solution stays rejected, and the next coding agent can already know why.
Live cross-repository decision graph:
https://keepthewhy.com/dashboard/live/#graph
Project:
https://github.com/oliver-zehentleitner/keep-the-why
#FOSS #OpenSource #CodingAgents #AIEngineering #Git #DevTools
Gitea 28.0.0 is here! 🚀
Starting with this release, we’re dropping the historical “1.” prefix — welcome to Gitea 28!
Highlights:
🔐 Audit logging
🤖 Dedicated bot accounts
🔑 HTTPS deploy tokens
👥 Code owner approval rules
🔍 PR diff search & filters
⚡ Actions queue view & artifact previews
🛠️ And much more
A huge thank you to everyone who contributed to this release! ❤️
Read the full release notes:
https://blog.gitea.com/release-of-28.0.0/
A codebase is more than code.
It is the result of decisions, rejected alternatives, production constraints and workarounds that made sense at the time.
With Keep the Why, that reasoning lives as plain Markdown in the repository and can reference reasoning in other repositories.
Once those links exist, something interesting emerges: a web of project rationale you can actually walk.
Families show where reasoning belongs.
Friends show where projects relate.
Thoughts show how decisions connect over time.
No graph database.
No central index.
No account.
Just Markdown and Git.
https://blog.technopathy.club/the-reasoning-behind-a-codebase-as-a-web-you-can-walk
#AI #AIAgents #CodingAgents #Git #OpenSource #SoftwareArchitecture #DeveloperTools #DevTools
JOB : nous recherchons un⋅e #adminsys senior avec les compétences suivantes => https://dali.bo/202609_offre_adminsys
✅ système et virtualisation : #linux #proxmox…
✅ sécurité : #vpn, routage…
✅ automatisation : #ansible #terraform ou #opentofu
✅ télé-collaboration : #git #dolibarr…
#Git 2.56 Adds New Options for Cleaning Up Branches and Resolving Conflicts https://9to5linux.com/git-2-56-adds-new-options-for-cleaning-up-branches-and-resolving-conflicts
A real commit history from a real project:
fix
fix again
actually fix
revert "actually fix"
please
WORKS
Squash before the merge request. Nobody needs to see what I went through.
#MemeMonday #Git #DevOps #Linux
Cool project:
A #git remote helper that stores an end-to-end #encrypted mirror of a git #repository on any ordinary git host. The host sees only opaque AEAD-encrypted blobs: no file contents, no filenames, no commit messages, no branch names, no history graph. Local repositories stay plain git. #privacy #code #storage #antiai
If you are sad about having missed my tutorial introducing users to the #Git compatible version control system #GameOfTrees at #EuroBSDcon two weeks ago, you can download the full tutorial instructions and work through all the same steps as people did in the room with me:
Little tip when linking to source code in your docs, etc.
You can link directly to lines using anchors if the web view of your source control system supports it. e.g., for Codeberg:
https://codeberg.org/small-tech/jsdb/src/branch/main/lib/QuerySanitiser.js#L264
However, that’s brittle and will break as you add/remove code above it.
A more robust way is to use text fragments, which are newly available across major browsers¹. e.g.,
The latter links to the same place and will also break if, say, you remove the method or rename it, but it will survive code changes in the rest of the file.
#dev #tip #git #codeberg #textFragments #URLs #linking #code #sourceControl
This project is still hosted on the centralized,
not-federated,
almost-monopolistic,
#git server of microsoft.
Another day, another patch received that I cannot apply cleanly because it was sent from a @protonprivacy email.
https://git-send-email.io/#step2
It’s going to the point where I will need to ask people that want to contribute to my project to use their gmail address instead…
I believe that wrong support for format=flowed is, at least, partly responsible for that.
We are starting to provide an unrestricted (fair-use) amount of hosted mailing lists with each subscription. See https://gothub.org/lists.html
We want to make use of mailing lists easy for projects which are starting out today, or have to migrate away from a mailing list server which is being shut down.
Our mailing list infrastructure is kept completely separate from our #Git hosting infrastructure. You can use mailing lists without having to use any of our version control features.
You can use your own domain name instead of lists.gothub.org if you want to.
Public lists can be archived. Private mail is only stored on our servers while in transit.
The mailing list server is hosted on #OpenBSD, running on our hardware in #Berlin, Germany.
@servo
So much **independent** that you host your files at #Microsoft #git server, *right ?*
I can't donate to projects hosted down there.
#OverUnder 083 with @irgndsondepp
He shares his thoughts on #GuitarHero, #podman, #FOMO, #Jujutsu and #cappuccino.
He replied to @etp's question
And, of course, we got #books recommendation.
#bloggers #bookstodon #book #blog #fediverse #mastodon #food #blogging #docker #git #coffee
Damn y’all, trying to find a great guide for fiction writers that want to use #Git and I haven’t found a single one that is well written, nor explains everything, like I’m torn between having every new sentence on its own line or keeping lengthy paragraphs as they are. From my understanding, git can’t review lengthy paragraphs so every new sentence must happen on their own limes. This is very easy to do with regular expressions, but absolutely none of the guides explain details like that and it’s compelled me to make my own that is going to handhold the user through everything. Too many guides written today assume that the reader knows what you are talking about and the more technical guides I read, the more handholding explanations I am after. Like yes I know how email travels but I want the guy to remind me by explaining it to me again even though I already know it
Actually, I'd love to check if what I know about scrapers in my corner of the internet applies to others. Is there anyone hosting a git forge large enough to be bothered by scrapers but small enough to be interested in experimenting with something?
I'd love to talk. Contacts / mentions appreciated!
#scrapers #git #devops
Actually, I'd love to check if what I know about scrapers in my corner of the internet applies to others. Is there anyone hosting a git forge large enough to be bothered by scrapers but small enough to be interested in experimenting with something?
I'd love to talk. Contacts / mentions appreciated!
#scrapers #git #devops
Our paper, with @plumtrie and M. Marcozzi, on how CI can stop #backdoor injection in source code at commit (or release) time using fuzzing, is now available: https://arxiv.org/abs/2607.26719
It comes with real, working code that FOSS projects and #security auditors can adopt. The paper artifact shows how effective it is on real-world, historical backdoors.
« Not In My #Git Yard: Catching Backdoors at Commit and Release Time » to be presented at #ASE2026, later this year.
Migration de Github vers une alternative européenne
https://eventuallycoding.com/p/migration-de-github-vers-une-alternative-europeenne
#git
Pushin: a new Git hosting that never leaves Europe - Public and private Git repos, hosted 100% in the EU, on a Platform built for Humans, not AI ; for now, in invite-only Beta #Git #Hosting https://pushin.eu/
je me suis penché pour la première fois ce soir sur les objets stockés dans #git et comment ils sont manipulés "sous le capot".
WOW.
je trouve ça ultra-élégant et ça rend les opérations de base quasiment accessibles au plus bas niveau, genre avec quelques outils en shell (de quoi faire des hash et des contenus zip) et beaucoup de patience (et beaucoup de manips intermédiaires, mais quand même, c'est gérable).
Ça m'a même ouvert les yeux sur le contenu du reflog et comment m'en servir.
A couple of tweaks on my `openremote` function, to deal with gitlab and overleaf cases:
```bash
openremote () {
if [ "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]
then
remote=$(git remote -v | grep origin | grep fetch | awk '{print $2}' | sed 's/ssh/https/g')
case "$remote" in
(*gitlab*) # We need to process things a bit more
echo "Gitlab: Removing colons from repository"
remote="http://$(echo $remote | awk -F@ '{print $2}'|sed 's/:/\//g')"
open $remote
;;
(*overleaf*) # Let's get the project ID
overleaf_id=$(echo $remote | awk -F/ '{print $4}')
open "https://www.overleaf.com/project/$overleaf_id"
;;
(*http*) # Normal https repository
open "$remote"
;;
(*)
echo "Git repository has no remote."
;;
esac
else
echo "Not inside a git repository."
fi
}
```
Updated on my Codeberg dotfiles project:
« TL;DR: we spend more CPU cycles rendering commits for scrapers than we spend on all other kinds of legitimate access, including git clones. At any one time, across 5 geo-distributed nodes, there are 14 CPU cores doing nothing but rendering git commits as html. »
Konstantin Ryabitsev , Creepy crawlies
Et la phrase qui tue : « With a bunch of generous assumptions, legitimate requests are only about 2% of git.kernel.org traffic — everything else are scrapers. » 😱😱😱
Pushin.eu is a European-based #Git hosting platform that ensures code remains within the #EU to avoid foreign legal reach like the CLOUD Act. The service is currently in an invite-only beta phase with general availability planned for early 2027. The project aims to provide developers with a reliable, human-centric alternative to global competitors.
A year of progress on the #git-based package #workflow. What's changed? What's still transitioning? What's next? #oSC26 https://youtu.be/1NXntvTWD5A
Ah c'est vraiment bien cette idée d'inverser le concept du gitignore pour **tout** ignorer par défaut, et n'inclure que les choses qu'on veut explicitement. https://packagemain.tech/p/gitignore-everything-by-default #git #configuration #optimisation #idée
#GitSocial: #Git-native collaboration platform
GitSocial is a CLI/TUI Go binary that stores issues, PRs, and other collaboration in git itself, as commits with structured trailers on gitmsg/* branches.
On top of its core design, that offers identity, static site generation, and notifications, there are a range of extensions:
I'm curious...
> git add --interactive
| never heard about it: | 8 |
| know it, in theory: | 5 |
| used it a couple of times: | 6 |
| part of my git workflow: | 8 |
Hi folks, I really enjoy Mastodon. It does remind me of the olden days of #irc and the #BBS era (in a good way).
I teach computer engineering technology at the University of Kentucky. I'm originally from #Germany.
My main interests here:
#technology
#softwareEngineering
#git
#linux
#unix
#science
#engineering
#astronomy
#audioEngineering
#electromagnetics
#ieee
#hamRadio
Dix schémas de projets open-source (Mastodon, GitLab, Cal.com…) en diagrammes ER, reconstruits depuis leur historique git
https://blog.mcdview.dev/fr/schemas-open-source-dans-la-nature/
#opensource #git
Can someone more knowledgeable with #git then I am tell me what kind of psychopath you have to be to forbid `wip` commits in pre-commit hooks or if there’s an actual reason behind it ?
It’s the second time I’m trying to work on a code-base that does this, and I’m stuck having to choose between:
- having disgusting commit messages
- constantly toggle git-hooks to just be able to *save my recent progress*
- just… not commit anything and risk messing things up
As someone who likes to move fast, try things out then only afterwards slow down, cleanup my work and squash commits together; not being able to make `wip` commits causes a huge amount of friction.
boostedhttps://sourcehut.org/blog/2026-08-27-tos-changes-and-llms/
#Sourcehut announces terms of service changes in relation to LLMs / AI.
I just realized that it only checks if a folder is a git repository... but if it is a repository, it does not check if there is a remote: it assumes there is, and fails when there is not. This is a fixed version:
```bash
openremote () {
if [ "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]
then
remote=$(git remote -v | grep origin | grep fetch | awk '{print $2}' | sed 's/ssh/https/g')
case "$remote" in
(*http*)
open "$remote"
;;
(*)
echo "Git repository has no remote."
;;
esac
else
echo "Not inside a git repository."
fi
}
```
This is a small bash/zsh function I made a couple of years ago because I wanted to be able to automatically open the web page of the forge for the remote. Tested it and it works not just with Github and Gitlab, but also with Codeberg, and I guess any other similar code forge.
```bash
function openremote {
if [ "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]
then
open $(git remote -v | grep origin | grep fetch | awk '{print $2}' | sed 's/ssh/https/g')
else
echo "Not inside a git repository."
fi
}
```
You just call it inside of a Git repository, and if there is a remote set, it will use the fetch link to create the web page to open. This works even for ssh remotes.
In Linux or *BSD, you can change `open` for something like `xdg-open` or `exo-open` for a desktop agnostic replacement, or `gnome-open`/`kde-open`, if you use any of those desktop environments.
[$] How to be safe from quantum computing
Practical quantum computers have been ten years away for the last several decades. Now, however, it's beginning to look as though they will be possible in just a few years. Recent [...]
https://lwn.net/Articles/1088305/
#LWN #Linux #security #Debian #RedHat #ArchLinux #Git #Firefox #OpenSSH
@pawelgrzybek Know that there's also `:qc` to quit with a non-zero status code. Comes in handy when your editor in called from another tool that relie on error code to know if the operation went well. I use it quite a lot to tell #git not to commit even if the message is valid.
Like many devs, I've been using #git for years.
I was then introduced to #jj and happily used it instead for month.
I came back to #git because some colleague's history shenanigans made #jj cry and I did not want to fight the tool.
And now, I realize I'm perfectly happy with #git anyway.
Because the issue has never been #git, it has always been us not following our own conventions.
Both #git and #jj are great tools.
We just suck at using them.
I really like Simon Harrison's series of blog posts about using #GameOfTrees for simple version control tasks: https://simonh.uk/tags/got/index.html
My own use cases are more complicated than Simon's but it is making me happy to see confirmation of how the UI designed for working on #OpenBSD and related projects is working very well for people with fairly simple needs. That was one of my goals from the very beginning and is a significant differentiator from #Git.
Dis-moi 
Sur git, y'a un moyen de voir d'un coup toutes les branches où on a des commits pas poussés sur le repository distant ?
(et au pire, branche par branche, je me disais que git status donnerait cette information, mais en fait non)
[$] Bootstrappable builds: how and why
This year's edition of the Free and Open Source Software Yearly conference, better known as "FOSSY", moved north to the beautiful (and enormous) campus of the University of British [...]
@KinkyKobolds mostly because "Tech-Illiterates" are lazy af…
Even a Mailinglist is better than Discord, because the latter one is an information blackhole that actively prevents archiving and searching.
Lazyness is NEVER an argument against proper tech!
#IRC #XMPP #Mumble #JitsiMeet #VoiceChat #Chat #VideoChat #MailingList #InformationBalckhole #archival #search #Zulip #RocketChat #Zammad #git #MkDocs #ntfy #MicroaoftTeams #Skype #lazyness
Git is great at storing dotfiles. It is less good at knowing where they belong, which permissions they need, or why a work laptop and a home server should differ.
Here is how I use chezmoi plus Git to manage fish, Neovim, SSH, GnuPG, Atuin and more. Including the “oops, I edited the live file” recovery workflow.
https://blog.hofstede.it/chezmoi-and-git-dotfiles-without-pretending-every-machine-is-the-same/
✍️ The story of a 50x optimization I made in Git earlier this year.
https://adamj.eu/tech/2026/08/07/git-stash-p-optimization-story/
✍️ List the files present in any Git commit without checking it out.
✍️ New post covering how to read your local Git log while skipping commits from a certain author. In my case, it was the ol’ Dependabot.
And in Activitypub I'm sure there are a lot of features specific to code handling that likely aren't supported. That's why it seems to me that unless either protocol has a major rewrite with this specific usecase in mind, that we're going to have to Frankenstein this.
What protocol should federated code forges use?
#EvanPoll #poll #federation #git
| ActivityPub: | 14 |
| ATProto: | 0 |
| Git: | 4 |
| Other (please specify): | 1 |
Git tip: Create a `.gitmessage` template file and set it with `git config commit.template ~/.gitmessage`. Consistent commit messages improve team communication and project history. #Git
RE: https://social.tchncs.de/@codefloe/116963861098218609
Although I appreciate what Codeberg does, I also recommend CodeFloe. I've been using it for several months now and it has works flawlessly!
It's particularly suited for your non-Open Source software and they don't have an Anti-AI clause.
Bonus for better uptime in my experience.
Our Tech Talk is back, hosted by Michelle Sebek - Head of Marketing NA.
We're kicking it off with the most honest demo environment there is: a real house with real pets. 🏡🐈
Mathias, one of our Solutions Engineers, has one rule for his smart home: he should be the only reason the lights don't turn on. Not a cloud outage. Not a vendor abandoning a perfectly working device.
Everything runs locally:
🏠 #HomeAssistant
📊 VictoriaMetrics
📂 Alerting rules in #Git
📲 Notifications through ntf
Super cool project;
https://github.com/epheterson/Zimi
It's an alternate front end for Kiwix's ZIM's. Auto updating through torrents with seeding, catalogue search, tons of built ins, like calendar, sky and space data. ZIM's are sorted by category, with custom sorting and favourites.
It even pulls random data for some ZIM's, like "word of the day" or "this day in history".
The world map ZIM works amazing with search and random locations, although a bit slow on a Pi5.
Something I've found really interesting is from the home screen you can click the random button and it'll give you a random article from all your ZIM's.
A big bonus is the dev is very friendly!
Game of Trees 0.127 released https://undeadly.org/cgi?action=article;sid=20260721102106 #openbsd #gameoftrees #got #git #versioncontrol #development #freesoftware #libresoftware
Git tip: Use `git commit --fixup <hash>` for small fixes, then `git rebase -i --autosquash` to automatically organize them. Keeps commit history clean during development. #Git
So git-remote-iroh works, but it's basically a toy demoware. I mean, you can push and pull over iroh, which is cool, but it's not this hub-breaking new thing that changes development workflows and defeats corporate hegemony over open-source software. The server mode is still a centralized hub.
I've been thinking this week about where to take it next, if I should at all. Where my head is at:
All repository clones could be remote peers that you can pull from. It should be easy to do this from a background process that spawns and stays running in the background. Could be on-demand, like how podman and gpg-agent do.
Because it's pull-only, it should be safe to serve this up from a clone with a working tree.
Hubs allow pushes, but don't attempt to force a single history. They are a synchronization point for blobs, tracking who has what blobs. All remote refs. What this does, is remove the need for everyone being online all the time.
Who decides what is the true timeline then? Up to a peer that decides to act as a publisher, and who follows it. What's nice about this, is you can have a primary and following replicas. You could even have multiple such primaries, possibly with different policies.
#git #iroh #p2p #nohubsjustspokes
1/
This is your periodic reminder that all the code you browse via the web UI of something like a #git repository doesn't necessarily match what you get via a git clone. In fact it's really easy to serve a trojan that's only in the git clone view so if you need to inspect code do it on the pulled copy.
Of course I can also only serve the trojan version to selected IP ranges matching a given corporation too. Isn't supply chain trust fun !
That's this alias: https://adamj.eu/tech/2022/10/30/git-how-to-clean-up-squash-merged-branches/ #Git
git stync
WARNING: You called a Git command named 'stync', which does not exist.
Continuing under the assumption that you meant 'sync'.
I will be hosting a #GameOfTrees version control system tutorial at #EuroBSDCon 2026, with @op as co-host.
This tutorial will be suitable for both #Git experts and complete beginners. The experts will probably spend significant effort temporarily unlearning some things they know, while the beginners will spend moderate effort learning some things they didn't know. Our goal is that both groups will broaden their version control horizons a bit and have fun doing so
Serve & clone #git repositories #p2p over #iroh! Try it out:
cargo install git-remote-iroh
git clone iroh://92fbc10667b6ae60b2b7c158ec3c996ebdeac0f07d6648b87243fe49498bd378 git-remote-iroh
git-remote-iroh is self-hosted. #distributed #dweb #nohubsjustspokes
Centralized web mirror: https://codeberg.org/cmars/git-remote-iroh
After long hiatus, gitg, a GTK git client, received new major release!
It includes many long-awaited changes, such as accessibility and performance improvements, full support for git push action and custom actions!
Get it on Flathub!!! https://flathub.org/en/apps/org.gnome.gitg
Coté Source :
~614 487 IP sources : rappel, on est sûr du logiciel NON grand publique, un peu niche avec zéro contribution de dev externe a l'entreprise, ce qui est normale.
Si j'enlève les IP de l'infra (monitoring, jenkins, redmine) on enlève ~630 000 requêtes pour 6 IPs.
reste 2 500 000 requêtes et 614 481 IPs ...
~ 582 000 IPs, on fait moins de 10 requêtes (pour un total de 1754808 requêtes soit plus de 50%) dans les détails :
~ 257 998 IPs, on fait une seule requête pour un total de 257998.
36395 IPs, on fait seulement 2 requêtes pour un total de 72790
125627 IPs, on fait seulement 3 requêtes pour un total de 376881
28233 IPs, on fait seulement 4 requêtes pour un total de 112932
15122 IPs, on fait seulement 5 requêtes pour un total de 75610
60216 IPs, on fait seulement 6 requêtes pour un total de 361296
sinon on est ~ une trentaine (et pas tous dev) et en ce lundi de juillet, les bureaux parisiens (ou il y a pas grand monde ~ 3 personnes) ont fait environ 800 requêtes...
donc l'usage "légitime" sur la journée doit être ~ 30 000 requêtes (évaluation haute) soit 1% de l'usage. (bon l'infra compte pour 20% quand même 🙂 )
bref, on n'est pas sur les mêmes chiffres, mais on dépasse largement ton test.
Plusieurs point : l'url du git est ancienne (depuis plus de 10 ans) il y a eu quelques changements, mais globalement ce sont les mêmes urls.
De toute façon, c'est seulement depuis moins de 2 ans qu'on a un nombre de requêtes aussi importantes. Au point de déclencher des erreurs sur le monitoring et d'empêcher l'usage correct de la plateforme.
Je pense que les robots ne sont pas ceux des moteurs de recherche, ils ne parcourent pas internet à la recherche de page a indexé, mais plutôt des robots qui ciblent des URLS particulières " à forte valeur ajoutée" (des urls de code opensource accessible, super pour alimenter des IAs de code).
Appel à bonnes âmes 😁
Mon compagnon, cet homme incroyable, m'a fait un script python pour me permettre de tamponner des pièces de procédure en 3 secondes.
En ayant parlé à d'autres, il s'avère qu'iels seraient intéressé.e.s mais ne sont pas sous linux (cheh)
J'ai deux questions :
- où mettre son dépôt git pour pouvoir le partager
- est-ce qu'il y a des trucs pour pouvoir faire fonctionner facilement ce truc sans passer par un terminal => le rendre humain compatible 😁 et éventuellement mac et windows accessible
Tout en réalisant le traitement sur le PC et non en ligne (secret pro 4ever)
Merci d'avance pour votre aide
Git tip: `git bisect` automates finding the commit that introduced a bug. Start with `git bisect start`, mark good/bad commits, and Git will binary search through history to find the culprit. #Git
J'aimerais dire que j'ai un quelconque mérite dans le process, mais je peut juste dire que j'ai des collègues formidables !!
#iso27001
Comme chaque année au 24ème, nous faisons des dons à des logiciels libres.
Cette année nous avons pu aider 38 projets : https://github.com/24eme/banque/blob/master/data/dons.csv
#Fatfree #Pulsar #Yunohost #Framasoft #Borg #Debian #tinc #php #etherpad #gnome #git #organicmaps #mumble #fdroid #kitty #signal #ripgrep #fzf #fd #tpope #comaps #mastodon #liberachat #Couchdb #SponsorBlock #Anubis #GrapheneOS #GNU #FFMPEG #Logseq #FairScan #NewPipe #Arch #GadgetBridge #FossifyCalendar #Letsencrypt #Phpactor #Sudo
1/2 🔽
#Git tip: `git stash push -m "description"` saves work-in-progress with a description. Use `git stash list` to see all stashes, `git stash pop stash@{0}` to apply a specific one.
#Git 2.55.0 is out: https://lore.kernel.org/all/xmqqv7b1w9vr.fsf@gitster.g/
For a overviews on new features see:
* @lwn: What's coming in Git 2.55 – https://lwn.net/Articles/1079596/
* GitLab: What's new in Git 2.55.0? – https://about.gitlab.com/blog/whats-new-in-git-2-55-0/
* GitHub: Highlights from Git 2.55 – https://github.blog/open-source/git/highlights-from-git-2-55/
Toulouse: Conserver l'historique d'un projet mené à plusieurs avec GIT, Le samedi 4 juillet 2026 de 14h00 à 18h00. https://www.agendadulibre.org/events/35444 #git #github #gitlab #versioning #caféBricol #atelier
#Linux #Bash #git
git: clone commit pull push … und dann?
Meistens macht Git einen Vorschlag wenn was nicht funktioniert hat.
Git-Kommandos, die ich gern benutze. Weil ich sehr schluderig tippe, gibts öfters Typos, Statt commit funktionirt besser …
https://gist.github.com/dewomser/5e1a699f48bff1153536a8d4bf0bd979
Git tip: Use `git log --oneline --graph` to visualize your branch history as a simple tree. Helps you understand merge patterns and spot where branches diverged or converged. #Git
Version control best practice: Write commit messages that complete the sentence "If applied, this commit will..." This creates clear, actionable descriptions of what each change does. #Git #VersionControl
Gitea 1.26.3 and 1.26.4 are now available.
1.26.3 includes security fixes, bug fixes, and stability improvements.
1.26.4 fixes a repository code-page regression introduced in 1.26.3, plus one additional security fix.
We recommend upgrading.
https://blog.gitea.com/release-of-1.26.3-and-1.26.4/
Given these days you can't even expect #Gentoo contributors to be respectable, I'm working on adding a git hook that rejects commits with #LLM attribution. Could you help me find all the common patterns used to mark LLM-assisted #git commits?
So far I'm checking for author and Co-authored-by using the following e-mail patterns:
• copilot@github.com
• *@anthropic.com
• claude@users.noreply.github.com
• *+claude[bot]@users.noreply.github.com
• *@openai.com
• *+chatgpt-codex-connector[bot]@users.noreply.github.com
• *@cursor.com
• *@x.ai
• *@google.com
I think some people came up with some other tags to mark LLM commits but can't find that right now.
Rhâââ !
Ce matin, j’ouvre mon éditeur de code (aka IDE), et une notification me dit :
> « GitLens upgraded to 18 – the Commit Graph is all new with agent integration, multi-worktree WIP rows, AI-powered Review and Compose modes, and more. »
Qu’est-ce que tu vas foutre de la %@&#$ d’IA dans une interface à #Git, espèce de débile !
Je n’en peux plus, de cette vague IA pourrie et de son forçage…
(merci d’avoir reçu l’expression de ma colère et mon exaspération, MastoPsy…)