<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xml:base="https://www.programmez.com/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Git</title>
    <link>https://www.programmez.com/</link>
    <description></description>
    <language>fr</language>
    
    <item>
  <title>Git 2.56 : nouveau --resolved, option --reset-when-found</title>
  <link>https://www.programmez.com/actualites/git-256-nouveau-resolved-option-reset-when-found-40214</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git 2.56 : nouveau --resolved, option --reset-when-found&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-09-29T07:58:33+02:00&quot; title=&quot;Mardi, 29 septembre 2026 - 07:58&quot; class=&quot;datetime&quot;&gt;mar, 29 Sep 2026 - 07:58&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-256-nouveau-resolved-option-reset-when-found-40214%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-256-nouveau-resolved-option-reset-when-found-40214%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

      &lt;div class=&quot;field field--name-field-image-actualite field--type-entity-reference field--label-hidden field__items&quot;&gt;
              &lt;div class=&quot;field__item&quot;&gt;&lt;div&gt;
  
  
  &lt;div class=&quot;field field--name-field-media-image field--type-image field--label-visually_hidden&quot;&gt;
    &lt;div class=&quot;field__label visually-hidden&quot;&gt;Image&lt;/div&gt;
              &lt;div class=&quot;field__item&quot;&gt;  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/styles/large/public/images_actus/git256.png.webp?itok=Z2PLfn4A&quot; class=&quot;image-style-large&quot; /&gt;


&lt;/div&gt;
          &lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;
          &lt;/div&gt;
  
            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Git annonce la version 2.56. Cette mise à jour inclut plusieurs nouvelles commandes et options :&lt;/p&gt;
&lt;p&gt;--reset-when-found dans la commande bisect : exécution automatiquement bsect rest pour revenir à l&#039;état initial&lt;/p&gt;
&lt;p&gt;--delete merge dans la commande branch : supprimer les branches locales déjà fusionnées&lt;/p&gt;
&lt;p&gt;git branch -d : indique qu&#039;une branche ne peut être supprimée car utilisée dans une recherche bsect&lt;/p&gt;
&lt;p&gt;--resolved : nouvelle option dans la commande add.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;$ git add --resolvedfatal: the following paths still have conflict markers:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; recipe.txt$ # Edit recipe.txt and remove the conflict markers.$ git add --resolved$ git status --short&amp;nbsp;M notes.txtM &amp;nbsp;recipe.txtGit 2.56 comptabilise le nombre de commits en attente réservés à chaque branche. Bien que l&#039;implémentation intègre des mécanismes de sécurité supplémentaires, en résumé, une fois qu&#039;une branche exclusive est épuisée, aucun nouveau point de rencontre ne peut apparaître. Git peut ainsi s&#039;arrêter tout en renvoyant chaque base de fusion.&amp;nbsp;La différence peut être spectaculaire lorsque d&#039;anciennes branches latérales ont été fusionnées dans un historique beaucoup plus long.&amp;nbsp;Autre novueauté : résolution d&#039;un problème de performance persistant du noyau Linux.&amp;nbsp;Annonce complète :&amp;nbsp;&lt;a href=&quot;https://github.blog/open-source/git/highlights-from-git-2-56/&quot;&gt;https://github.blog/open-source/git/highlights-from-git-2-56/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Tue, 29 Sep 2026 05:58:33 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">82250 at https://www.programmez.com</guid>
    </item>
<item>
  <title>git guess : deviner le type de vos commits, sans cloud et sans clé d&#039;API</title>
  <link>https://www.programmez.com/actualites/git-guess-deviner-le-type-de-vos-commits-sans-cloud-et-sans-cle-dapi-40163</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;git guess : deviner le type de vos commits, sans cloud et sans clé d&amp;#039;API&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-09-22T15:26:09+02:00&quot; title=&quot;Mardi, 22 septembre 2026 - 15:26&quot; class=&quot;datetime&quot;&gt;mar, 22 Sep 2026 - 15:26&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-guess-deviner-le-type-de-vos-commits-sans-cloud-et-sans-cle-dapi-40163%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-guess-deviner-le-type-de-vos-commits-sans-cloud-et-sans-cle-dapi-40163%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

      &lt;div class=&quot;field field--name-field-image-actualite field--type-entity-reference field--label-hidden field__items&quot;&gt;
              &lt;div class=&quot;field__item&quot;&gt;&lt;div&gt;
  
  
  &lt;div class=&quot;field field--name-field-media-image field--type-image field--label-visually_hidden&quot;&gt;
    &lt;div class=&quot;field__label visually-hidden&quot;&gt;Image&lt;/div&gt;
              &lt;div class=&quot;field__item&quot;&gt;  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/styles/large/public/images_actus/demo.png.webp?itok=kaRYmlih&quot; class=&quot;image-style-large&quot; /&gt;


&lt;/div&gt;
          &lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;
          &lt;/div&gt;
  
            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Actualité par&lt;strong&gt; Jean-François Lépine&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Si votre équipe utilise les&lt;a href=&quot;https://www.conventionalcommits.org/&quot;&gt; Conventional Commits&lt;/a&gt;, vous connaissez sans doute le problème. Le format s&#039;apprend en cinq minutes, mais le choix du type reste une affaire d&#039;interprétation. Corriger un bug en réécrivant la fonction, est-ce un fix ou un refactor ? Une montée de dépendance, un build ou un chore ? Chacun répond à sa manière, et les linters ne sont d&#039;aucun secours, puisqu&#039;ils vérifient la syntaxe du message sans regarder le contenu du changement. Au bout de quelques mois, le changelog raconte une histoire approximative et les releases automatiques calculent des numéros de version à partir de types choisis à l&#039;instinct.&lt;/p&gt;

&lt;p&gt;J&#039;ai fini par me dire que la seule source fiable était le diff lui-même. Comme j’aime bien m’amuser à monter des modèles IA, j&#039;ai écrit&lt;a href=&quot;https://github.com/Halleck45/git-guess&quot;&gt; git guess&lt;/a&gt; pour résoudre ce problème.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pourquoi je l&#039;ai fait ?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Il existe déjà beaucoup d&#039;outils qui écrivent des messages de commit. La plupart envoient votre diff à un LLM hébergé dans le cloud, ce qui suppose de transmettre votre code à un tiers, y compris ce qui n&#039;est pas encore commité, et de gérer une clé d&#039;API pour un simple préfixe de message. Je n&#039;en avais pas envie.&lt;/p&gt;
&lt;p&gt;J&#039;ai donc pris le chemin inverse et construit un outil souverain, qui ne dépend d&#039;aucune IA externe. Le modèle est embarqué dans le binaire, tout tourne en local et rien ne quitte votre machine. Je le voulais aussi très simple à adopter, avec un seul binaire (écrit en Go), sans dépendance, sans compte et sans configuration. Enfin je le voulais rapide, parce qu&#039;une commande qui s&#039;intercale dans git commit n&#039;a pas le droit de se faire remarquer. La réponse tombe en une trentaine de millisecondes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Comment ça marche ?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Le modèle a été entraîné sur 488 000 commits provenant de 244 projets open source, qui lui donnent sa culture générale. Il apprend ensuite des 1 000 derniers commits de votre dépôt, qui lui apportent la culture de votre équipe. Si chez vous les migrations partent en chore, git guess les classera en chore au lieu d&#039;imposer sa propre vision. Concrètement, il lit le diff, le compare à ce qu&#039;il connaît et propose un type accompagné d&#039;un score de confiance.&lt;/p&gt;
&lt;p&gt;git guess&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # que contiennent mes changements indexés ?&lt;/p&gt;
&lt;p&gt;git guess -m &quot;add login&quot; &amp;nbsp; &amp;nbsp; &amp;nbsp; # feat(auth): add login&lt;/p&gt;
&lt;p&gt;git guess HEAD~1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # un commit, ou une plage main..feature&lt;/p&gt;
&lt;p&gt;git guess eval &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; # quelle précision sur mon propre historique ?&lt;/p&gt;
&lt;p&gt;Au passage, ça supporte également les &lt;a href=&quot;https://gitmoji.dev/&quot;&gt;gitmoji&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Au quotidien&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Mon mode d&#039;utilisation préféré reste le hook, qui s&#039;installe en une commande :&lt;/p&gt;
&lt;p&gt;git guess hook install&lt;/p&gt;
&lt;p&gt;À partir de là, l&#039;outil se fait oublier. Un git commit -m &quot;add login&quot; devient feat(auth): add login, et un git commit sans argument ouvre votre éditeur avec le type déjà rempli. Quand la décision est serrée, une seule question s&#039;affiche, du genre ? fix 41% or refactor 38%? [f/r], et vous y répondez d&#039;une touche. J&#039;ai aussi posé une règle stricte dès la conception : le hook ne bloque jamais un commit, parce qu&#039;un outil qui se met en travers d&#039;un correctif urgent finit désinstallé avant la fin de la semaine.&lt;/p&gt;
&lt;p&gt;En intégration continue, une action GitHub reprend le même moteur pour étiqueter vos pull requests à partir de leur diff et vérifier les commits d&#039;une branche. Une ligne suffit : uses: Halleck45/git-guess@v1.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Est-ce que ça marche vraiment ?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Sur des dépôts que le modèle n&#039;a jamais vu, j&#039;obtiens 70 % de bonnes réponses au premier choix et 88 % dans les deux premiers. C’est, je crois, suffisant, d’autant que je voulais garder le modèle simple et léger.&amp;nbsp;La commande git guess eval rejoue l&#039;historique de votre dépôt et mesure combien de fois l&#039;outil aurait retrouvé le type que votre équipe avait réellement choisi, ce qui vous permet de juger sur votre propre code avant d&#039;adopter quoi que ce soit. J&#039;ai d&#039;ailleurs remarqué que les cas où l&#039;outil hésite sont presque toujours ceux où l&#039;équipe hésitait déjà.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Installation&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;brew install Halleck45/tap/git-guess&lt;/p&gt;
&lt;p&gt;#&amp;nbsp;ou&lt;/p&gt;
&lt;p&gt;curl -fsSL https://raw.githubusercontent.com/Halleck45/git-guess/main/install.sh | sh&lt;/p&gt;
&lt;p&gt;#&amp;nbsp;ou&lt;/p&gt;
&lt;p&gt;npx git-guess&lt;/p&gt;
&lt;p&gt;Des binaires sont disponibles pour Linux, macOS et Windows (amd64, arm64) sur la page des releases, et le projet est publié sous licence MIT.&amp;nbsp;Le projet est tout jeune, et le meilleur moyen de m&#039;aider est de le tester sur vos dépôts, puis de me dire ce que git guess eval vous raconte. Les retours, bons ou mauvais, sont ce qui fait vivre un outil open source.&lt;/p&gt;
&lt;p&gt;Dépôt :&lt;a href=&quot;https://github.com/Halleck45/git-guess&quot;&gt; https://github.com/Halleck45/git-guess&lt;br&gt;&lt;/a&gt;Documentation :&lt;a href=&quot;https://halleck45.github.io/git-guess/&quot;&gt; https://halleck45.github.io/git-guess/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Tue, 22 Sep 2026 13:26:09 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">82224 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Git 2.55 : Rust devient le langage par défaut</title>
  <link>https://www.programmez.com/actualites/git-255-rust-devient-le-langage-par-defaut-39650</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git 2.55 : Rust devient le langage par défaut&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-06-17T10:51:42+02:00&quot; title=&quot;Mercredi, 17 juin 2026 - 10:51&quot; class=&quot;datetime&quot;&gt;mer, 17 Jun 2026 - 10:51&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-255-rust-devient-le-langage-par-defaut-39650%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-255-rust-devient-le-langage-par-defaut-39650%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Git introduit une bascule importante à partir de la version 2.55 : Rust est activé par défaut. C&#039;est donc un choix assumé et la fin du C dans la plateforme. On aura (encore) la possibilité de faire du opt-out sur le support Rust : dans le makerfile, le dév peut choisir entre WITH_RUST ou NO_RUST. Attention : à partir de 3.0, Rust ne pourra pas être désactivé. Cette version annonce donc un profond changement et prépare la génération de Rust.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;La 2.55 inclut 397 commits non fusionnés depuis la 2.54.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Note de version suite à la disponibilité de la version rc0 :&amp;nbsp;&lt;a href=&quot;https://lore.kernel.org/lkml/xmqqik7pqeiq.fsf@gitster.g/&quot;&gt;https://lore.kernel.org/lkml/xmqqik7pqeiq.fsf@gitster.g/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Wed, 17 Jun 2026 08:51:42 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">81807 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Git 2.54 introduit en expérimentation la commande git history</title>
  <link>https://www.programmez.com/actualites/git-254-introduit-en-experimentation-la-commande-git-history-39350</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git 2.54 introduit en expérimentation la commande git history&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-04-21T08:23:07+02:00&quot; title=&quot;Mardi, 21 avril 2026 - 08:23&quot; class=&quot;datetime&quot;&gt;mar, 21 Avr 2026 - 08:23&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-254-introduit-en-experimentation-la-commande-git-history-39350%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-254-introduit-en-experimentation-la-commande-git-history-39350%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

      &lt;div class=&quot;field field--name-field-image-actualite field--type-entity-reference field--label-hidden field__items&quot;&gt;
              &lt;div class=&quot;field__item&quot;&gt;&lt;div&gt;
  
  
  &lt;div class=&quot;field field--name-field-media-image field--type-image field--label-visually_hidden&quot;&gt;
    &lt;div class=&quot;field__label visually-hidden&quot;&gt;Image&lt;/div&gt;
              &lt;div class=&quot;field__item&quot;&gt;  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/styles/large/public/images_actus/git254.png.webp?itok=0ILwyLwh&quot; class=&quot;image-style-large&quot; /&gt;


&lt;/div&gt;
          &lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;
          &lt;/div&gt;
  
            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Git annonce la version 2.54. La principale fonctionnalitée est la commande git history. Attention, pour le moment, elle est en expérimentation. git history est là pour &quot;réécrire&quot; l&#039;histoire des référentiels Git. On peut déjà réorganiser un dépôt avec la fameuse commande rebase. Pour des cas plus simples, rebase semble trop complexe et avec trop d&#039;options. La commande history est là pour modifier le dépôt : par exemple, corriger une faute dans un texte de commit ancien ou encore scinder un commit en deux, etc. Cette commande supporte pour le moment reword et split.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;git history reword &amp;lt;commit&amp;gt; : ouvre l&#039;éditeur avec le commit spécifié et on peut le réécrire. Il mettra à jour les branches dépendantes. La commande ne modifie par le tree ou l&#039;index de travail&lt;/p&gt;
&lt;p&gt;git history split &amp;lt;commit&amp;gt; : permet de scinder un commit en 2&amp;nbsp;&lt;/p&gt;
&lt;p&gt;$ git history split HEADdiff --git a/bar b/barnew file mode 100644index 0000000..50810a5--- /dev/null+++ b/bar@@ -0,0 +1 @@+bar(1/1) Stage addition [y,n,q,a,d,p,?]? y
&lt;/p&gt;&lt;p&gt;Git 2.24 permet maintenant de définir des hooks pouvant être partagé dans plusieurs dépôts et fichiers de configuration. Git introduit le concept de config basée sur les hooks.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;La liste des améliorations et ajustements est très longue :&lt;/p&gt;
&lt;pre&gt;* &quot;git add -p&quot; and friends note what the current status of the hunk
   being shown is.

 * &quot;git history&quot; history rewriting (experimental) command has been
   added.

 * &quot;git replay&quot; is taught to drop commits that become empty (not the
   ones that are empty in the original).

 * The help text and the documentation for the &quot;--expire&quot; option of
   &quot;git worktree [list|prune]&quot; have been improved.

 * When &quot;git show-index&quot; is run outside a repository, it silently
   defaults to SHA-1; the tool now warns when this happens.

 * &quot;git merge-file&quot; can be run outside a repository, but it ignored
   all configuration, even the per-user ones.  The command now uses
   available configuration files to find its customization.

 * &quot;auto filter&quot; logic for large-object promisor remote.

 * &quot;git rev-list&quot; and friends learn &quot;--maximal-only&quot; to show only the
   commits that are not reachable by other commits.

 * Command line completion (in contrib/) update for
   &quot;stash import/export&quot;.

 * &quot;git repo info&quot; learns &quot;--keys&quot; action to list known keys.

 * Extend the alias configuration syntax to allow aliases using
   characters outside ASCII alphanumeric (plus &#039;-&#039;).

 * A signature on a commit that was GPG signed a long time ago ought to
   be still valid after the key that was used to sign it has expired,
   but we showed them in alarming red.

 * &quot;git subtree split --prefix=P &amp;lt;commit&amp;gt;&quot; now checks the prefix P
   against the tree of the (potentially quite different from the
   current working tree) given commit.

 * &quot;git add -p&quot; learned a new mode that allows the user to revisit a
   file that was already dealt with.

 * Allow the directory in which reference backends store their data to
   be specified.

 * &quot;gitweb&quot; has been taught to be mobile friendly.

 * &quot;git apply --directory=./un/../normalized/path&quot; now normalizes the
   given path before using it.

 * &quot;git maintenance&quot; starts using the &quot;geometric&quot; strategy by default.

 * &quot;git config list&quot; is taught to show the values interpreted for
   specific type with &quot;--type=&amp;lt;X&amp;gt;&quot; option.

 * &quot;git add &amp;lt;submodule&amp;gt;&quot; has been taught to honor
   submodule.&amp;lt;name&amp;gt;.ignore that is set to &quot;all&quot; (and requires &quot;git add
   -f&quot; to override it).

 * Hook commands are now allowed to be defined (possibly centrally)
   in the configuration files, and run multiple of them for the same
   hook event.

 * The way end-users can add their own &quot;git &amp;lt;cmd&amp;gt;&quot; subcommand by
   storing &quot;git-&amp;lt;cmd&amp;gt;&quot; in a directory on their $PATH has not been
   documented clearly, which has been corrected.

 * &quot;git send-email&quot; learns to pass hostname/port to Authen::SASL
   module.

 * &quot;git send-email&quot; learns to support use of client-side certificates.

 * &quot;git send-email&quot; has learned to be a bit more careful when it
   accepts charset to use from the end-user, to avoid &#039;y&#039; (mistaken
   &#039;yes&#039; when expecting a charset like &#039;UTF-8&#039;) and other nonsense.

 * &quot;git status&quot; learned to show comparison between the current branch
   and various other branches listed on status.compareBranches
   configuration.

 * &quot;git repo structure&quot; command learns to report maximum values on
   various aspects of objects it inspects.

 * &quot;git rebase&quot; learns &quot;--trailer&quot; option to drive the
   interpret-trailers machinery.

 * &quot;git fast-import&quot; learned to optionally replace signature on
   commits whose signatures get invalidated due to replaying by
   signing afresh.

 * &quot;git history&quot; learned the &quot;split&quot; subcommand.

 * The reference-transaction hook was taught to be triggered before
   taking locks on references in the &quot;preparing&quot; phase.

 * &quot;git apply&quot; now reports the name of the input file along with the
   line number when it encounters a corrupt patch, and correctly
   resets the line counter when processing multiple patch files.

 * The HTTP transport learned to react to &quot;429 Too Many Requests&quot;.

 * &quot;git repo info -h&quot; and &quot;git repo structure -h&quot; limit their help output
   to the part that is specific to the subcommand.

 * &quot;git format-patch --cover-letter&quot; learns to use a simpler format
   instead of the traditional shortlog format to list its commits with
   a new --commit-list-format option and format.commitListFormat
   configuration variable.

 * `git backfill` learned to accept revision and pathspec arguments.

 * &quot;git replay&quot; (experimental) learns, in addition to &quot;pick&quot; and
   &quot;replay&quot;, a new operating mode &quot;revert&quot;.

 * &quot;git replay&quot; now supports replaying down to the root commit.

 * Handling of signed commits and tags in fast-import has been made more
   configurable.

 * &quot;git config list&quot; is the official way to spell &quot;git config -l&quot; and
   &quot;git config --list&quot;.  Use it to update the documentation.&lt;/pre&gt;&lt;p&gt;De nombreuses pull requests, et bugs, ont été fixés dans cette 2.24.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Note de version complète :&amp;nbsp;&lt;a href=&quot;https://lore.kernel.org/lkml/xmqqa4uxsjrs.fsf@gitster.g/&quot;&gt;https://lore.kernel.org/lkml/xmqqa4uxsjrs.fsf@gitster.g/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Le résumé de GitHub :&amp;nbsp;&lt;a href=&quot;https://github.blog/open-source/git/highlights-from-git-2-54/&quot;&gt;https://github.blog/open-source/git/highlights-from-git-2-54/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Tue, 21 Apr 2026 06:23:07 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78881 at https://www.programmez.com</guid>
    </item>
<item>
  <title>gitpulsar : une GUI Git pour gérer Git sur GNOME</title>
  <link>https://www.programmez.com/actualites/gitpulsar-une-gui-git-pour-gerer-git-sur-gnome-39307</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;gitpulsar : une GUI Git pour gérer Git sur GNOME&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-04-13T09:50:04+02:00&quot; title=&quot;Lundi, 13 avril 2026 - 09:50&quot; class=&quot;datetime&quot;&gt;lun, 13 Avr 2026 - 09:50&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/gitpulsar-une-gui-git-pour-gerer-git-sur-gnome-39307%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/gitpulsar-une-gui-git-pour-gerer-git-sur-gnome-39307%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Pour gérer les dépôts Git sur GNOME, il existe une GUI dédiée : gitpulsar. Elle est écrite en Rust, GTK et libadwaita. La dernière version distribuée est la 0.6.0. Elle améliore le fonctionnement en arrière-plan, le cache.&amp;nbsp;gitpulsar supporte les multi-dépôts, l&#039;historique des commits, la colorisation de la syntaxe, merge &amp;amp; rebase, auto-refresh, etc.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Le projet est disponible sur GitLab :&amp;nbsp;&lt;a href=&quot;https://gitlab.com/ilshat-apps/gitpulsar&quot;&gt;https://gitlab.com/ilshat-apps/gitpulsar&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Liste des fonctionnalités Git supportées :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Multi-repo workspace&lt;/strong&gt;&amp;nbsp;— open a folder, browse all Git repositories inside&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit history&lt;/strong&gt;&amp;nbsp;— searchable list with expandable details, paginated loading&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit detail&lt;/strong&gt;&amp;nbsp;— prominent message display, file list with configurable limit, collapsible technical details&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Branch graph&lt;/strong&gt;&amp;nbsp;— visual branch topology in a separate window&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Staging area&lt;/strong&gt;&amp;nbsp;— split unstaged/staged lists with drag-and-drop, per-file and per-hunk stage/unstage/discard&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Partial staging&lt;/strong&gt;&amp;nbsp;— stage/unstage individual hunks within a file&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Syntax highlighting&lt;/strong&gt;&amp;nbsp;— language-aware diff coloring with dark/light theme support&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Undo/redo&lt;/strong&gt;&amp;nbsp;— undo staging operations and file discards (Ctrl+Z / Ctrl+Shift+Z)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Branch management&lt;/strong&gt;&amp;nbsp;— create, checkout local/remote branches&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remote operations&lt;/strong&gt;&amp;nbsp;— fetch, pull, push via git CLI (reliable SSH support)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stash&lt;/strong&gt;&amp;nbsp;— save, pop, list, drop&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit editing&lt;/strong&gt;&amp;nbsp;— amend, edit message, cherry-pick, revert&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit signing&lt;/strong&gt;&amp;nbsp;— signed commit indicator (lock icon)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge &amp;amp; rebase&lt;/strong&gt;&amp;nbsp;— conflict detection, continue/abort merge and rebase&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Interactive rebase&lt;/strong&gt;&amp;nbsp;— reorder, squash, fixup, reword, drop commits&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Submodules&lt;/strong&gt;&amp;nbsp;— list, init, update submodules&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktrees&lt;/strong&gt;&amp;nbsp;— list, add, remove git worktrees&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;.gitignore editor&lt;/strong&gt;&amp;nbsp;— edit .gitignore from the app menu&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Adaptive layout&lt;/strong&gt;&amp;nbsp;— 3-tier responsive design: desktop, tablet (&amp;lt;860sp), mobile (&amp;lt;500sp). Minimum 360px width&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auto-refresh&lt;/strong&gt;&amp;nbsp;— configurable polling with hash-based skip&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Preferences&lt;/strong&gt;&amp;nbsp;— date format, refresh interval, commit files limit&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Mon, 13 Apr 2026 07:50:04 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78840 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Tangled : le Git européen lève 3,8 millions</title>
  <link>https://www.programmez.com/actualites/tangled-le-git-europeen-leve-38-millions-39087</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Tangled : le Git européen lève 3,8 millions&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-03-04T10:27:44+01:00&quot; title=&quot;Mercredi, 4 mars 2026 - 10:27&quot; class=&quot;datetime&quot;&gt;mer, 4 Mar 2026 - 10:27&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/tangled-le-git-europeen-leve-38-millions-39087%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/tangled-le-git-europeen-leve-38-millions-39087%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Tangled est une plateforme Git, ou plutôt une plateforme sociale collaborative Git comme le présente Tangled. Le service est construit sur le protcocole AT. La plateforme se veut décentraliser. Elle vise 3 objectifs :&lt;/p&gt;
&lt;p&gt;- les données sont uniquement à vous&lt;/p&gt;
&lt;p&gt;- un coût le plus bas possible&lt;/p&gt;
&lt;p&gt;- pas de compromis sur l&#039;UX : ce qui veut tout dire et rien dire.&lt;/p&gt;
&lt;p&gt;Pour construire une telle plateforme, il faut des équipes, des développeurs et une solide infrastructure. Pour soutenir le projet, Tangled annonce avoir levé 3,8 millions € auprès de Bain Capital Crypto, Antler, Thomas Dohmke (ancien CEO de GitHub), Avery Pennarun (Tailscale). Ce financement doit permettre de :&lt;/p&gt;
&lt;p&gt;- de reconstruire toute la CI en utilisant des micro-VM&lt;/p&gt;
&lt;p&gt;- améliorer le protocole&lt;/p&gt;
&lt;p&gt;- améliorer le tableau de bord des PR, des issues et tous les éléments des référentiels&lt;/p&gt;
&lt;p&gt;- créer un outil pour migrer de GitHub à Tangled&lt;/p&gt;
&lt;p&gt;- déployer toutes les fonctionnalités de recherche&lt;/p&gt;
&lt;p&gt;- construire la Tangled CLI&lt;/p&gt;
&lt;p&gt;Site :&amp;nbsp;&lt;a href=&quot;https://tangled.org/&quot;&gt;https://tangled.org/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Pour en savoir plus sur le protocole AT :&amp;nbsp;&lt;a href=&quot;https://atproto.com/&quot;&gt;https://atproto.com/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Wed, 04 Mar 2026 09:27:44 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78692 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Git 2.53 : nouvelles sous-commandes, bug fix, optimisations</title>
  <link>https://www.programmez.com/actualites/git-253-nouvelles-sous-commandes-bug-fix-optimisations-38969</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git 2.53 : nouvelles sous-commandes, bug fix, optimisations&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2026-02-04T11:40:29+01:00&quot; title=&quot;Mercredi, 4 février 2026 - 11:40&quot; class=&quot;datetime&quot;&gt;mer, 4 Fév 2026 - 11:40&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-253-nouvelles-sous-commandes-bug-fix-optimisations-38969%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-253-nouvelles-sous-commandes-bug-fix-optimisations-38969%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Git déploie la version 2.53. Cette mise à jour apporte des nouveautés fonctionnelles et diverses optimisations. Parmi les nouveautés, retenons :&lt;/p&gt;
&lt;p&gt;- une nouvelle sous-commande is-need dabs la commande git maintenance s&#039;il est nécessaire de faire différents tâches de maintenance&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- option --diff-algorithm= dans la commande git blame et option --all dans git repo&lt;/p&gt;
&lt;p&gt;- commande expérimentale git replay&lt;/p&gt;
&lt;p&gt;- optimisation sur les sous-commandes et les opérations&lt;/p&gt;
&lt;p&gt;- amélioration sur les messages d&#039;erreurs&lt;/p&gt;
&lt;p&gt;- nombreuses corrections de bugs&lt;/p&gt;
&lt;p&gt;La note de version complète :&lt;/p&gt;
&lt;p&gt;Git v2.53 Release Notes=======================UI, Workflows &amp;amp; Features------------------------&amp;nbsp;* &quot;git maintenance&quot; command learned &quot;is-needed&quot; subcommand to tell if&amp;nbsp; &amp;nbsp;it is necessary to perform various maintenance tasks.&amp;nbsp;* &quot;git replay&quot; (experimental) learned to perform ref updates itself&amp;nbsp; &amp;nbsp;in a transaction by default, instead of emitting where each refs&amp;nbsp; &amp;nbsp;should point at and leaving the actual update to another command.&amp;nbsp;* &quot;git blame&quot; learns &quot;--diff-algorithm=&amp;lt;algo&amp;gt;&quot; option.&amp;nbsp;* &quot;git repo info&quot; learned &quot;--all&quot; option.&amp;nbsp;* Both &quot;git apply&quot; and &quot;git diff&quot; learn a new whitespace error class,&amp;nbsp; &amp;nbsp;&quot;incomplete-line&quot;.&amp;nbsp;* Add a new manual that describes the data model.&amp;nbsp;* &quot;git fast-import&quot; learns &quot;--signed-commits=strip-if-invalid&quot; option&amp;nbsp; &amp;nbsp;to drop invalid cryptographic signature from objects.&amp;nbsp;* The use of &quot;revision&quot; (a connected set of commits) has been&amp;nbsp; &amp;nbsp;clarified in the &quot;git replay&quot; documentation.&amp;nbsp;* A help message from &quot;git branch&quot; now mentions &quot;git help&quot; instead of&amp;nbsp; &amp;nbsp;&quot;man&quot; when suggesting to read some documentation.&amp;nbsp;* &quot;git repo struct&quot; learned to take &quot;-z&quot; as a synonym to &quot;--format=nul&quot;.&amp;nbsp;* More object database related information are shown in &quot;git repo&amp;nbsp; &amp;nbsp;structure&quot; output.&amp;nbsp;* Improve the error message when a bad argument is given to the&amp;nbsp; &amp;nbsp;`--onto` option of &quot;git replay&quot;. &amp;nbsp;Test coverage of &quot;git replay&quot; has&amp;nbsp; &amp;nbsp;been improved.&amp;nbsp;* The iconv library on macOS fails to correctly handle stateful&amp;nbsp; &amp;nbsp;ISO/IEC 2022:1994 encoded strings. &amp;nbsp;Work it around instead of&amp;nbsp; &amp;nbsp;replacing it wholesale from homebrew.&amp;nbsp;* Upstream symbolic link support on Windows from Git-for-Windows.Performance, Internal Implementation, Development Support etc.--------------------------------------------------------------&amp;nbsp;* The list of packfiles used in a running Git process is moved from&amp;nbsp; &amp;nbsp;the packed_git structure into the packfile store.&amp;nbsp;* Some ref backend storage can hold not just the object name of an&amp;nbsp; &amp;nbsp;annotated tag, but the object name of the object the tag points at.&amp;nbsp; &amp;nbsp;The code to handle this information has been streamlined.&amp;nbsp;* As &quot;git diff --quiet&quot; only cares about the existence of any&amp;nbsp; &amp;nbsp;changes, disable rename/copy detection to skip more expensive&amp;nbsp; &amp;nbsp;processing whose result will be discarded anyway.&amp;nbsp;* A part of code paths that deals with loose objects has been cleaned&amp;nbsp; &amp;nbsp;up.&amp;nbsp;* &quot;make strip&quot; has been taught to strip &quot;scalar&quot; as well as &quot;git&quot;.&amp;nbsp;* Dockerized jobs at the GitHub Actions CI have been taught to show&amp;nbsp; &amp;nbsp;more details of failed tests.&amp;nbsp;* Code refactoring around object database sources.&amp;nbsp;* Halve the memory consumed by artificial filepairs created during&amp;nbsp; &amp;nbsp;&quot;git diff --find-copies-harder&quot;, also making the operation run&amp;nbsp; &amp;nbsp;faster.&amp;nbsp;* The &quot;git_istream&quot; abstraction has been revamped to make it easier&amp;nbsp; &amp;nbsp;to interface with pluggable object database design.&amp;nbsp;* Rewrite the only use of &quot;mktemp()&quot; that is subject to TOCTOU race&amp;nbsp; &amp;nbsp;and Stop using the insecure &quot;mktemp()&quot; function.&amp;nbsp; &amp;nbsp;(merge 10bba537c4 rs/ban-mktemp later to maint).&amp;nbsp;* In-code comment update to clarify that single-letter options are&amp;nbsp; &amp;nbsp;outside of the scope of command line completion script.&amp;nbsp; &amp;nbsp;(merge dc8a00fafe jc/completion-no-single-letter-options later to maint).&amp;nbsp;* MEMZERO_ARRAY() helper is introduced to avoid clearing only the&amp;nbsp; &amp;nbsp;first N bytes of an N-element array whose elements are larger than&amp;nbsp; &amp;nbsp;a byte.&amp;nbsp;* &quot;git diff-files -R --find-copies-harder&quot; has been taught to use&amp;nbsp; &amp;nbsp;the potential copy sources from the index correctly.&amp;nbsp;* Require C99 style flexible array member support from all platforms.&amp;nbsp;* The code path that enumerates promisor objects have been optimized&amp;nbsp; &amp;nbsp;to skip pointlessly parsing blob objects.&amp;nbsp;* Prepare test suite for Git for Windows that supports symbolic&amp;nbsp; &amp;nbsp;links.&amp;nbsp;* Import newer version of &quot;clar&quot;, unit testing framework.&amp;nbsp; &amp;nbsp;(merge 84071a6dea ps/clar-integers later to maint).&amp;nbsp;* The packfile_store data structure is moved from object store to odb&amp;nbsp; &amp;nbsp;source.&amp;nbsp;* The object-info API has been cleaned up.&amp;nbsp;* Further preparation to upstream symbolic link support on Windows.&amp;nbsp;* Remove implicit reliance on the_repository global in the APIs&amp;nbsp; &amp;nbsp;around tree objects and make it explicit which repository to work&amp;nbsp; &amp;nbsp;in.&amp;nbsp;* &quot;git bugreport&quot; and &quot;git version --build-options&quot; learned to&amp;nbsp; &amp;nbsp;include use of &#039;gettext&#039; feature, to make it easier to diagnose&amp;nbsp; &amp;nbsp;problems around l10n.&amp;nbsp;* Dscho observed that SVN tests are taking too much time in CI leak&amp;nbsp; &amp;nbsp;checking tasks, but most time is spent not in our code but in libsvn&amp;nbsp; &amp;nbsp;code (which happen to be written in Perl), whose leaks have little&amp;nbsp; &amp;nbsp;value to discover for us. &amp;nbsp;Skip SVN, P4, and CVS tests in the leak&amp;nbsp; &amp;nbsp;checking tasks.&amp;nbsp; &amp;nbsp;(merge 047bd7dfe3 js/ci-leak-skip-svn later to maint).Fixes since v2.52-----------------&amp;nbsp;* Ever since we added whitespace rules for this project, we misspelt&amp;nbsp; &amp;nbsp;an entry, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 358e94dc70 jc/gitattributes-whitespace-no-indent-fix later to maint).&amp;nbsp;* The code to expand attribute macros has been rewritten to avoid&amp;nbsp; &amp;nbsp;recursion to avoid running out of stack space in an uncontrolled&amp;nbsp; &amp;nbsp;way.&amp;nbsp; &amp;nbsp;(merge 42ed046866 jk/attr-macroexpand-wo-recursion later to maint).&amp;nbsp;* Adding a repository that uses a different hash function is a no-no,&amp;nbsp; &amp;nbsp;but &quot;git submodule add&quot; did not prevent it, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 6fe288bfbc bc/submodule-force-same-hash later to maint).&amp;nbsp;* An earlier check added to osx keychain credential helper to avoid&amp;nbsp; &amp;nbsp;storing the credential itself supplied was overeager and rejected&amp;nbsp; &amp;nbsp;credential material supplied by other helper backends that it would&amp;nbsp; &amp;nbsp;have wanted to store, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 4580bcd235 kn/osxkeychain-idempotent-store-fix later to maint).&amp;nbsp;* The &quot;git repo structure&quot; subcommand tried to align its output but&amp;nbsp; &amp;nbsp;mixed up byte count and display column width, which has been&amp;nbsp; &amp;nbsp;corrected.&amp;nbsp; &amp;nbsp;(merge 7a03a10a3a jx/repo-struct-utf8width-fix later to maint).&amp;nbsp;* Yet another corner case fix around renames in the &quot;ort&quot; merge&amp;nbsp; &amp;nbsp;strategy.&amp;nbsp; &amp;nbsp;(merge a562d90a35 en/ort-rename-another-fix later to maint).&amp;nbsp;* Test leakfix.&amp;nbsp; &amp;nbsp;(merge 14b561e768 jk/test-mktemp-leakfix later to maint).&amp;nbsp;* Update a version of action used at the GitHub Actions CI.&amp;nbsp; &amp;nbsp;(merge cd99203f86 js/ci-github-setup-go-update later to maint).&amp;nbsp;* The &quot;return errno = EFOO, -1&quot; construct, which is heavily used in&amp;nbsp; &amp;nbsp;compat/mingw.c and triggers warnings under &quot;-Wcomma&quot;, has been&amp;nbsp; &amp;nbsp;rewritten to avoid the warnings.&amp;nbsp; &amp;nbsp;(merge af3919816f js/mingw-assign-comma-fix later to maint).&amp;nbsp;* Makefile based build have recently been updated to build a&amp;nbsp; &amp;nbsp;libgit.a that also has reftable and xdiff objects; CMake based&amp;nbsp; &amp;nbsp;build procedure has been updated to match.&amp;nbsp; &amp;nbsp;(merge b0d5c88cca js/cmake-libgit-fix later to maint).&amp;nbsp;* Under-allocation fix.&amp;nbsp; &amp;nbsp;(merge d22a488482 js/wincred-get-credential-alloc-fix later to maint).&amp;nbsp;* &quot;git worktree list&quot; attempts to show paths to worktrees while&amp;nbsp; &amp;nbsp;aligning them, but miscounted display columns for the paths when&amp;nbsp; &amp;nbsp;non-ASCII characters were involved, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 08dfa59835 pw/worktree-list-display-width-fix later to maint).&amp;nbsp;* &quot;Windows+meson&quot; job at the GitHub Actions CI was hard to debug, as&amp;nbsp; &amp;nbsp;it did not show and save failed test artifacts, which has been&amp;nbsp; &amp;nbsp;corrected.&amp;nbsp; &amp;nbsp;(merge 17bd1108ea jk/ci-windows-meson-test-fix later to maint).&amp;nbsp;* Emulation code clean-up.&amp;nbsp; &amp;nbsp;(merge 2367c6bcd6 gf/win32-pthread-cond-wait-err later to maint).&amp;nbsp;* Various issues detected by Asan have been corrected.&amp;nbsp; &amp;nbsp;(merge a031b6181a jk/asan-bonanza later to maint).&amp;nbsp;* &quot;git config get --path&quot; segfaulted on an &quot;:(optional)path&quot; that&amp;nbsp; &amp;nbsp;does not exist, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 0bd16856ff jc/optional-path later to maint).&amp;nbsp;* The &quot;--committer-date-is-author-date&quot; option of &quot;git am/rebase&quot; is&amp;nbsp; &amp;nbsp;a misguided one. &amp;nbsp;The documentation is updated to discourage its&amp;nbsp; &amp;nbsp;use.&amp;nbsp; &amp;nbsp;(merge fbf3d0669f kh/doc-committer-date-is-author-date later to maint).&amp;nbsp;* The option help text given by &quot;git config unset -h&quot; described&amp;nbsp; &amp;nbsp;the &quot;--all&quot; option to &quot;replace&quot;, not &quot;unset&quot;, multiple variables,&amp;nbsp; &amp;nbsp;which has been corrected.&amp;nbsp; &amp;nbsp;(merge 18bf67b753 rs/config-unset-opthelp-fix later to maint).&amp;nbsp;* The error message given by &quot;git config set&quot;, when the variable&amp;nbsp; &amp;nbsp;being updated has more than one values defined, used old style &quot;git&amp;nbsp; &amp;nbsp;config&quot; syntax with an incorrect option in its hint, both of which&amp;nbsp; &amp;nbsp;have been corrected.&amp;nbsp; &amp;nbsp;(merge df963f0df4 rs/config-set-multi-error-message-fix later to maint).&amp;nbsp;* &quot;git replay&quot; forgot to omit the &quot;gpgsig-sha256&quot; extended header&amp;nbsp; &amp;nbsp;from the resulting commit the same way it omits &quot;gpgsig&quot;, which has&amp;nbsp; &amp;nbsp;been corrected.&amp;nbsp; &amp;nbsp;(merge 9f3a115087 pw/replay-exclude-gpgsig-fix later to maint).&amp;nbsp;* A few tests have been updated to work under the shell compatible&amp;nbsp; &amp;nbsp;mode of zsh.&amp;nbsp; &amp;nbsp;(merge a92f243a94 bc/zsh-testsuite later to maint).&amp;nbsp;* The way patience diff finds LCS has been optimized.&amp;nbsp; &amp;nbsp;(merge c7e3b8085b yc/xdiff-patience-optim later to maint).&amp;nbsp;* Recent optimization to &quot;last-modified&quot; command introduced use of&amp;nbsp; &amp;nbsp;uninitialized block of memory, which has been corrected.&amp;nbsp; &amp;nbsp;(merge fe4e60759b tc/last-modified-active-paths-optimization later to maint).&amp;nbsp;* &quot;git last-modified&quot; used to mishandle &quot;--&quot; to mark the beginning of&amp;nbsp; &amp;nbsp;pathspec, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 05491b90ce js/last-modified-with-sparse-checkouts later to maint).&amp;nbsp;* Emulation code clean-up.&amp;nbsp; &amp;nbsp;(merge 42aa7603aa gf/win32-pthread-cond-init later to maint).&amp;nbsp;* &quot;git submodule add&quot; to add a submodule under &amp;lt;name&amp;gt; segfaulted,&amp;nbsp; &amp;nbsp;when a submodule.&amp;lt;name&amp;gt;.something is already in .gitmodules file&amp;nbsp; &amp;nbsp;without defining where its submodule.&amp;lt;name&amp;gt;.path is, which has been&amp;nbsp; &amp;nbsp;corrected.&amp;nbsp; &amp;nbsp;(merge dd8e8c786e jc/submodule-add later to maint).&amp;nbsp;* &quot;git fetch&quot; that involves fetching tags, when a tag being fetched&amp;nbsp; &amp;nbsp;needs to overwrite existing one, failed to fetch other tags, which&amp;nbsp; &amp;nbsp;has been corrected.&amp;nbsp; &amp;nbsp;(merge b7b17ec8a6 kn/fix-fetch-backfill-tag-with-batched-ref-updates later to maint).&amp;nbsp;* Document &quot;rev-list --filter-provided-objects&quot; better.&amp;nbsp; &amp;nbsp;(merge 6d8dc99478 jt/doc-rev-list-filter-provided-objects later to maint).&amp;nbsp;* Even when there is no changes in the packfile and no need to&amp;nbsp; &amp;nbsp;recompute bitmaps, &quot;git repack&quot; recomputed and updated the MIDX&amp;nbsp; &amp;nbsp;file, which has been corrected.&amp;nbsp; &amp;nbsp;(merge 6ce9d558ce ps/repack-avoid-noop-midx-rewrite later to maint).&amp;nbsp;* Update HTTP tests to adjust for changes in curl 8.18.0&amp;nbsp; &amp;nbsp;(merge 17f4b01da7 jk/test-curl-updates later to maint).&amp;nbsp;* Workaround the &quot;iconv&quot; shipped as part of macOS, which is broken&amp;nbsp; &amp;nbsp;handling stateful ISO/IEC 2022 encoded strings.&amp;nbsp; &amp;nbsp;(merge cee341e9dd rs/macos-iconv-workaround later to maint).&amp;nbsp;* Running &quot;git diff&quot; with &quot;--name-only&quot; and other options that allows&amp;nbsp; &amp;nbsp;us not to look at the blob contents, while objects that are lazily&amp;nbsp; &amp;nbsp;fetched from a promisor remote, caused use-after-free, which has&amp;nbsp; &amp;nbsp;been corrected.&amp;nbsp;* The ort merge machinery hit an assertion failure in a history with&amp;nbsp; &amp;nbsp;criss-cross merges renamed a directory and a non-directory, which&amp;nbsp; &amp;nbsp;has been corrected.&amp;nbsp; &amp;nbsp;(merge 979ee83e8a en/ort-recursive-d-f-conflict-fix later to maint).&amp;nbsp;* Diagnose invalid bundle-URI that lack the URI entry, instead of&amp;nbsp; &amp;nbsp;crashing.&amp;nbsp; &amp;nbsp;(merge 7796c14a1a sb/bundle-uri-without-uri later to maint).&amp;nbsp;* Mailmap update for Karsten&amp;nbsp; &amp;nbsp;(merge e97678c4ef js/mailmap-karsten-blees later to maint).&amp;nbsp;* Perf-test fixes.&amp;nbsp; &amp;nbsp;(merge 79d301c767 jk/t-perf-fixes later to maint).&amp;nbsp;* Fix for a performance regression in &quot;git cat-file&quot;.&amp;nbsp; &amp;nbsp;(merge 9e8b448dd8 jk/cat-file-avoid-bitmap-when-unneeded later to maint).&amp;nbsp;* Update a FAQ entry on synching two separate repositories using the&amp;nbsp; &amp;nbsp;&quot;git stash export/import&quot; recently introduced.&amp;nbsp; &amp;nbsp;(merge 02fc44a989 bc/doc-stash-import-export later to maint).&amp;nbsp;* &quot;git fsck&quot; used inconsistent set of refs to show a confused&amp;nbsp; &amp;nbsp;warning, which has been corrected.&amp;nbsp;* Some error messages from the http transport layer lacked the&amp;nbsp; &amp;nbsp;terminating newline, which has been corrected.&amp;nbsp; &amp;nbsp;(merge a8227ae8d5 kt/http-backend-errors later to maint).&amp;nbsp;* &quot;git repack --geometric&quot; did not work with promisor packs, which&amp;nbsp; &amp;nbsp;has been corrected.&amp;nbsp;* The logic that avoids reusing MIDX files with a wrong checksum was&amp;nbsp; &amp;nbsp;broken, which has been corrected.&amp;nbsp;* Other code cleanup, docfix, build fix, etc.&amp;nbsp; &amp;nbsp;(merge 46207a54cc qj/doc-http-bad-want-response later to maint).&amp;nbsp; &amp;nbsp;(merge df90eccd93 kh/doc-commit-extra-references later to maint).&amp;nbsp; &amp;nbsp;(merge f18aa68861 rs/xmkstemp-simplify later to maint).&amp;nbsp; &amp;nbsp;(merge fddba8f737 ja/doc-synopsis-style later to maint).&amp;nbsp; &amp;nbsp;(merge 22ce0cb639 en/xdiff-cleanup-2 later to maint).&amp;nbsp; &amp;nbsp;(merge 8ef7355a8f je/doc-pull later to maint).&amp;nbsp; &amp;nbsp;(merge 48176f953f jc/capability-leak later to maint).&amp;nbsp; &amp;nbsp;(merge 8cbbdc92f7 kh/doc-pre-commit-fix later to maint).&amp;nbsp; &amp;nbsp;(merge d4bc39a4d9 mh/doc-config-gui-gcwarning later to maint).&amp;nbsp; &amp;nbsp;(merge 41d425008a kh/doc-send-email-paragraph-fix later to maint).&amp;nbsp; &amp;nbsp;(merge d4b732899e jc/macports-darwinports later to maint).&amp;nbsp; &amp;nbsp;(merge bab391761d kj/pull-options-decl-cleanup later to maint).&amp;nbsp; &amp;nbsp;(merge 007b8994d4 rs/t4014-git-version-string-fix later to maint).&amp;nbsp; &amp;nbsp;(merge 4ce170c522 ds/doc-scalar-config later to maint).&amp;nbsp; &amp;nbsp;(merge a0c813951a jc/doc-commit-signoff-config later to maint).&amp;nbsp; &amp;nbsp;(merge 8ee262985a ja/doc-misc-fixes later to maint).&amp;nbsp; &amp;nbsp;(merge 1722c2244b mh/doc-core-attributesfile later to maint).&amp;nbsp; &amp;nbsp;(merge c469ca26c5 dk/ci-rust-fix later to maint).&amp;nbsp; &amp;nbsp;(merge 12f0be0857 gf/clear-path-cache-cleanup later to maint).&amp;nbsp; &amp;nbsp;(merge 949df6ed6b js/test-func-comment-fix later to maint).&amp;nbsp; &amp;nbsp;(merge 93f894c001 bc/checkout-error-message-fix later to maint).&amp;nbsp; &amp;nbsp;(merge abf05d856f rs/show-branch-prio-queue later to maint).&amp;nbsp; &amp;nbsp;(merge 06188ea5f3 rs/parse-config-expiry-simplify later to maint).&amp;nbsp; &amp;nbsp;(merge 861dbb1586 dd/t5403-modernise later to maint).&amp;nbsp; &amp;nbsp;(merge acffc5e9e5 ja/doc-synopsis-style-more later to maint).&amp;nbsp; &amp;nbsp;(merge 6c5c7e7071 ac/t1420-use-more-direct-check later to maint).&amp;nbsp; &amp;nbsp;(merge 2ac93bfcbc ds/builtin-doc-update later to maint).&amp;nbsp; &amp;nbsp;(merge 3f051fc9c9 kh/doc-patch-id later to maint).&amp;nbsp; &amp;nbsp;(merge 555c8464e5 je/doc-reset later to maint).&amp;nbsp; &amp;nbsp;(merge 220f888d7e ps/t1410-cleanup later to maint).&amp;nbsp; &amp;nbsp;(merge 5814b04c02 ps/config-doc-get-urlmatch-fix later to maint).&amp;nbsp; &amp;nbsp;(merge 5ae594f30b sb/doc-update-ref-markup-fix later to maint).&amp;nbsp; &amp;nbsp;(merge bc8556d066 ty/t1005-test-path-is-helpers later to maint).&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Wed, 04 Feb 2026 10:40:29 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78587 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Git 3.0 sera une version de rupture avec Rust et SHA256</title>
  <link>https://www.programmez.com/actualites/git-30-sera-une-version-de-rupture-avec-rust-et-sha256-38587</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git 3.0 sera une version de rupture avec Rust et SHA256&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2025-11-18T18:09:53+01:00&quot; title=&quot;Mardi, 18 novembre 2025 - 18:09&quot; class=&quot;datetime&quot;&gt;mar, 18 Nov 2025 - 18:09&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-30-sera-une-version-de-rupture-avec-rust-et-sha256-38587%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-30-sera-une-version-de-rupture-avec-rust-et-sha256-38587%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

      &lt;div class=&quot;field field--name-field-image-actualite field--type-entity-reference field--label-hidden field__items&quot;&gt;
              &lt;div class=&quot;field__item&quot;&gt;&lt;div&gt;
  
  
  &lt;div class=&quot;field field--name-field-media-image field--type-image field--label-visually_hidden&quot;&gt;
    &lt;div class=&quot;field__label visually-hidden&quot;&gt;Image&lt;/div&gt;
              &lt;div class=&quot;field__item&quot;&gt;  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/styles/large/public/images_actus/git252.png.webp?itok=LnKIdDyN&quot; width=&quot;480&quot; height=&quot;252&quot; class=&quot;image-style-large&quot; /&gt;


&lt;/div&gt;
          &lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;
          &lt;/div&gt;
  
            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Git 3.0 n&#039;est pas attendu avant fin 2026 mais la communauté se prépare à une version de rupture avec une casse fonctionnelle qu&#039;il faudra anticipier. Pour le moment, Git est disponible en version 2.52. Elle introduit le début de la &lt;strong&gt;migration vers SHA1 vers SHA256&lt;/strong&gt; et l&#039;interoperabilité entre les deux. SHA256 arrivera avec Git 3. L&#039;autre changement majeur sera un changement de dénomination : main à la place de master.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;L&#039;autre nouveauté de Git 3 est l&#039;intégration de Rust&lt;/strong&gt; qui servira à la sécurité mémoire (le fameux safe memory). Il s&#039;agit d&#039;une importante évolution architecturale et Rust devient obligatoire. Jusqu&#039;à présent, Git était essentiellement codé en C. Les arguments sont toujours les mêmes : safe memory, outillage plus moderne, maintenabilité à long terme (là l&#039;argument est aussi valable pour le C). La v3 promet de nettes améliorations de performances sur les principales opérations comme le git-push. Plusieurs commandes encore expérimentales ne le seront plus avec la prochaine version.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Pour le moment, la 2.52 ne change pas la manière de travailler avec Git. Mais il ne faut pas hésiter à comprendre SHA-256 et à migrer vers les versions les plus récentes et à vérifier l&#039;ensemble des dépendances qui devront le supporter.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;La 2.52 améliore plusieurs commandes Git et on dispose d&#039;une nouvelle commande : git repo, git last-modified.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Annonce de la 2.52 :&amp;nbsp;&lt;a href=&quot;https://lore.kernel.org/lkml/xmqqh5usmvsd.fsf@gitster.g/&quot;&gt;https://lore.kernel.org/lkml/xmqqh5usmvsd.fsf@gitster.g/&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Tue, 18 Nov 2025 17:09:53 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78296 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Git : mettre des messages de Commit c&#039;est bien, faire des messages concrets c&#039;est mieux</title>
  <link>https://www.programmez.com/actualites/git-mettre-des-messages-de-commit-cest-bien-faire-des-messages-concrets-cest-mieux-38506</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Git : mettre des messages de Commit c&amp;#039;est bien, faire des messages concrets c&amp;#039;est mieux&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2025-11-07T11:41:20+01:00&quot; title=&quot;Vendredi, 7 novembre 2025 - 11:41&quot; class=&quot;datetime&quot;&gt;ven, 7 Nov 2025 - 11:41&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/git-mettre-des-messages-de-commit-cest-bien-faire-des-messages-concrets-cest-mieux-38506%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/git-mettre-des-messages-de-commit-cest-bien-faire-des-messages-concrets-cest-mieux-38506%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/commit&quot; hreflang=&quot;fr&quot;&gt;Commit&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Comment bien utiliser les messages dans son commit Git ? Si dans les logs, vous voyez uniquement : add, version finale, etc. Le message est aussi imprécis qu&#039;inutile. Un message de Commit mal écrit peut vite devenir problématique quand vous faites un debug ou quand vous remontez l&#039;historique ou simplement pour travailler en équipe. Exemple de commentaires qui n&#039;apporte rien : git commit -m &quot;optimisation du code&quot;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Qu&#039;est-ce que cela signifie réellement ? Si au moment de la rédaction du commit, on connait le contexte, ce message n&#039;aura plus de sens après quelques semaines ou même quelques jours. Donc : on perd le contexte, on ne comprend pas ce qu&#039;il a été fait dans le commit. Cela peut provoquer une perte de temps pour rentrer dans le code et comprendre le commit.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Bref : &lt;strong&gt;un message de commit clair et précis est toujours une bonne chose&lt;/strong&gt;. Cela peut faciliter la maintenance, le debug et aider à l&#039;équipe à comprendre ce qu&#039;il se passe.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Un bon message peut se structurer en 2 parties : ce qui change, et donner le contexte. La première partie peut utiliser des mots clés pour identifier immédiatement de quoi on parle, par exemple :&lt;/p&gt;
&lt;p&gt;feat -&amp;gt; pour une nouvelle fonctionnalité&lt;/p&gt;
&lt;p&gt;fix -&amp;gt; pour corriger quelque chose&lt;/p&gt;
&lt;p&gt;etc.&lt;/p&gt;
&lt;p&gt;Exemple : git commit -m &quot;feat(ticket-1973:implementation fonction login Ajout login utilisant AWS Cognito avec validation&lt;/p&gt;
&lt;p&gt;Le commentaire donne le contexte et sa nature : on ajoute une nouvelle fonctionnalité qui est sommairement décrite et liée à un ticket ouvert puis on décrit rapidement ce fait la nouvelle feature.&lt;/p&gt;
&lt;p&gt;Source :&amp;nbsp;&lt;a href=&quot;https://dev.to/thushar-p/git-commit-messages-that-makes-sense--4kff&quot;&gt;https://dev.to/thushar-p/git-commit-messages-that-makes-sense--4kff&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
      
    &lt;h2 class=&quot;title&quot;&gt;Commentaire actu&lt;/h2&gt;
    
  
  
&lt;article role=&quot;article&quot; data-comment-user-id=&quot;28559&quot; id=&quot;comment-19127&quot; class=&quot;comment js-comment clearfix&quot;&gt;

  &lt;div class=&quot;comment__meta col-sm-3&quot;&gt;
        &lt;span class=&quot;hidden text-danger&quot; data-comment-timestamp=&quot;1762942632&quot;&gt;&lt;/span&gt;
    &lt;article class=&quot;profile&quot;&gt;
  





  &lt;div class=&quot;js-form-item js-form-type-item form-type-item js-form-item- form-item- form-no-label mb-3&quot;&gt;
                    &lt;h4 class=&quot;label&quot;&gt;Membre depuis&lt;/h4&gt; 14 ans 2 mois
                      &lt;/div&gt;
&lt;/article&gt;

    &lt;small class=&quot;comment__author&quot;&gt;&lt;span&gt;labilbe&lt;/span&gt;&lt;/small&gt;
          &lt;/div&gt;

  &lt;div class=&quot;comment__content col-sm-9 card&quot;&gt;
    &lt;div class=&quot;card-body&quot;&gt;
              
        &lt;h3 class=&quot;card-title&quot;&gt;&lt;a href=&quot;/comment/19127#comment-19127&quot; class=&quot;permalink&quot; rel=&quot;bookmark&quot; hreflang=&quot;fr&quot;&gt;Voir l&amp;#039;excellente page de &lt;/a&gt;&lt;/h3&gt;
        
            
            &lt;div class=&quot;clearfix text-formatted field field--name-comment-body field--type-text-long field--label-hidden field__item&quot;&gt;&lt;p&gt;Voir l&#039;excellente page de &quot;Commits conventionnels&quot; afin de normer vos messages.&lt;/p&gt;
&lt;p&gt;https://www.conventionalcommits.org/fr/v1.0.0/&lt;/p&gt;
&lt;/div&gt;
      
              &lt;nav&gt;&lt;drupal-render-placeholder callback=&quot;comment.lazy_builders:renderLinks&quot; arguments=&quot;0=19127&amp;amp;1=default&amp;amp;2=fr&amp;amp;3=&quot; token=&quot;DeigTbHOK_3gIPsyaTpeXrkbW03gGx8x3_cI40SVsh8&quot;&gt;&lt;/drupal-render-placeholder&gt;&lt;/nav&gt;
          &lt;/div&gt;
    &lt;div class=&quot;card-body&quot;&gt;
      &lt;span class=&quot;comment__time&quot;&gt;mer, 12 Nov 2025 - 11:17&lt;/span&gt;
      &lt;span class=&quot;comment__permalink&quot;&gt;&lt;a href=&quot;/comment/19127#comment-19127&quot; hreflang=&quot;fr&quot;&gt;Permalien&lt;/a&gt;&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/article&gt;


  
&lt;/section&gt;
</description>
  <pubDate>Fri, 07 Nov 2025 10:41:20 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">78242 at https://www.programmez.com</guid>
    </item>
<item>
  <title>Gogs : déployer un serveur Git rapidement</title>
  <link>https://www.programmez.com/actualites/gogs-deployer-un-serveur-git-rapidement-38071</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;Gogs : déployer un serveur Git rapidement&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;span&gt;francoistonic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2025-08-06T09:24:13+02:00&quot; title=&quot;Mercredi, 6 août 2025 - 09:24&quot; class=&quot;datetime&quot;&gt;mer, 6 Aoû 2025 - 09:24&lt;/time&gt;
&lt;/span&gt;


  &lt;div class=&quot;inline__links&quot;&gt;&lt;nav class=&quot;links inline nav links-inline&quot;&gt;&lt;span class=&quot;comment-forbidden nav-link&quot;&gt;&lt;a href=&quot;/user/login?destination=/actualites/gogs-deployer-un-serveur-git-rapidement-38071%23comment-form&quot;&gt;Se connecter&lt;/a&gt; ou &lt;a href=&quot;/user/register?destination=/actualites/gogs-deployer-un-serveur-git-rapidement-38071%23comment-form&quot;&gt;s&#039;inscrire&lt;/a&gt; pour publier un commentaire&lt;/span&gt;&lt;/nav&gt;
  &lt;/div&gt;

&lt;div class=&quot;btn btn-light&quot;&gt;
      &lt;a href=&quot;/actualites/outils&quot; hreflang=&quot;fr&quot;&gt;Outils&lt;/a&gt;
  &lt;/div&gt;

&lt;div class=&quot;mots-cles-actualite d-flex flex-wrap gap-2&quot;&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/git&quot; hreflang=&quot;fr&quot;&gt;Git&lt;/a&gt;&lt;/div&gt;
      &lt;div class=&quot;btn&quot;&gt;&lt;a href=&quot;/actualites/gogs&quot; hreflang=&quot;fr&quot;&gt;Gogs&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;

            &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Et si on se passait des platesformes GitHub et GitLab par un service Git ? Déployer son propre Git n&#039;est pas toujours simple. Le projet Gogs est là pour nous simplifier la vie : Gogs permet de builder un service Git stable, extensible et auto-géré en évitant au maximum de complexifier l&#039;administration. Il supporte Go, macOS, Linux, Windows et les systèmes Arm.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Les principales fonctionnalités : tableau de bord, accès aux répertoires par SSH, HTTP, HTTPS, gestion des projets et référentiels, pull request, support Pupyter, rendu PDF, systèmes d&#039;authentification, etc. Bref, tout Git.&lt;/p&gt;
&lt;p&gt;Gogs peut se déployer directement sur une Pi, un service cloud ou Docker. Il faut une base de données installée, Git, un serveur SSH. On peut installer directement un binaire. Ainsi, on transforme un Pi 5 en serveur Git !&lt;/p&gt;
&lt;p&gt;Un tutoriel pour installer Gogs sur une Pi :&amp;nbsp;&lt;a href=&quot;https://dinodevs.com/blog/installing-gogs-git-server-on-raspberry-pi/&quot;&gt;https://dinodevs.com/blog/installing-gogs-git-server-on-raspberry-pi/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;GitHub :&amp;nbsp;&lt;a href=&quot;https://github.com/gogs/gogs&quot;&gt;https://github.com/gogs/gogs&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
      &lt;section class=&quot;field field--name-field-commentaire-actu field--type-comment field--label-above comment-wrapper&quot;&gt;
  
  

  
&lt;/section&gt;
</description>
  <pubDate>Wed, 06 Aug 2025 07:24:13 +0000</pubDate>
    <dc:creator>francoistonic</dc:creator>
    <guid isPermaLink="false">77900 at https://www.programmez.com</guid>
    </item>

  </channel>
</rss>
