home.social

#mergeconflict — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mergeconflict, aggregated by home.social.

fetched live
  1. Az új agents/ könyvtárba tervezett AI agent erőforrások a kernel coding assistantjaihoz gyűjtenék a promptokat és képességeket — elsőként LLM-alapú, a „Fixes:” tageket használó azonosítót javasolnak. Vajon gyorsabbá teszi ez a hibajavítást? Te használnád ilyen AI-t a kernel fejlesztésében?
    linuxmint.hu/hir/2026/10/uj-ai

    #LinuxKernel #AI #AIagents #agents #LLM #SashaLevin #NVIDIA #AGENTSmd #codingassistant #kernel-development #mergeconflict

  2. @OVargas
    In case of a #git #mergeConflict I first try rebasing it onto the target branch in #GitLab. If that's not possible, I use #TortoiseGit 🐢 for rebasing. Within 🐢 I then diff all the changes I've made in the remote feature branch and then compare them with a diff between the local feature branch and the remote target branch, which should be the same. Then see if everything locally still builds and if so, rewrite the feature branch.

    I just hate merge commits. 🤢

  3. If you've ever spent an hour resolving a merge conflict on a shared branch, you know the feeling of watching this piadina arrive at your table...

    #Rubycon2026 #Ruby #DevHumor #MergeConflict #Piadina

  4. i wrote this #python #cli #tool last year it's pretty good.

    #protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

    protokolo.readthedocs.io/en/st

    #development #programming #git

Share on Mastodon

Enter the server where you have an account.