🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)
🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)

🔧 Programmierung 🕛 kürzlich 6 Min Lesezeit
0

MergeForge: Resolve Git Conflicts in VS Code or Cursor Like in JetBrains

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

Tired of squinting at VS Code’s stacked merge editor?








The problem



We’ve all been there.



You’re halfway through a rebase. Git stops. Twelve files are conflicted. You open one in VS Code… and get that familiar stacked layout: Incoming, Current, and a result pane that somehow still feels like a puzzle with half the pieces missing.



If you ever used WebStorm or IntelliJ, you know how good merge tools can feel:




  • Your side on the left

  • Their side on the right

  • The result in the middle

  • Gutter arrows that just… work



In VS Code land, that flow never quite arrived. You click Accept Current, Accept Incoming, Accept Both, and hope nothing important got flattened. Word-level diffs? Authorship? A clear “who wrote this chunk?” signal? Often missing when you need them most.



And when AI entered the chat, a lot of tools treated conflicts like isolated text blobs:




“Here are the <<<<<<< markers. Good luck.”




But real merges need context. What was the branch trying to do? What does the surrounding file look like? Who touched this last? Without that, “AI resolve” is just confident guessing.



I wanted the JetBrains merge experience — inside VS Code and Cursor — with an assistant that behaves more like a careful teammate than a slot machine.



So I built it.






The solution: MergeForge








AI that reads your repo, not just the conflict markers



Explain conflicts, resolve them into the result pane, or Fix all (safe mechanical merges first, model only on the red chunks). The model can use read-only tools — open files, search code, inspect history, look up symbols — and you see live activity so nothing is a black box.



Works with:





  • GitHub Copilot in VS Code (Language Model API) out of the box

  • Or your own key for Anthropic, OpenAI, DeepSeek, Kimi/Moonshot, or any OpenAI-compatible endpoint (OpenRouter, local Ollama, proxies)



Keys live in VS Code secret storage. Nothing hits git until you hit Apply. Unhappy with an AI edit? Undo that chunk like any other change.








Built with care (and tests)



MergeForge is TypeScript end to end:





  • VS Code Extension API for commands, SCM, secret storage, and Copilot LM integration


  • Monaco Editor inside the webview for the three panes


  • node-diff3 + a custom chunking engine checked against real git merge-file output


  • Vercel AI SDK for multi-provider streaming and tool use


  • esbuild for the extension + webview bundles


  • Vitest for unit, git-parity, and end-to-end tests



The correctness bar matters: where git merges cleanly, MergeForge aims to match git byte for byte. There’s also a replay eval for the AI pipeline so prompt changes can be regression-checked against real historical merges.




CODE
git clone https://github.com/ognjenmarcheta/merge-forge.git
cd merge-forge
pnpm install
pnpm test
pnpm run watch # then F5 to launch the Extension Development Host









Open source & contributions welcome



MergeForge is MIT-licensed and fully open source.



Repo:
VS Code



Source, issues, stars




Next time git yells CONFLICT (content), open the file and forge the branches back into one piece.






Your turn



What’s the worst merge conflict you’ve ever had to untangle — and what should MergeForge add next: better multi-file orchestration, more keyboard power-user flows, or deeper AI “why did this conflict?” narratives?



Drop a comment. I read them all.

Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Hackers Just Poisoned the Rust Supply Chain | Threat Wire
1 Quelle
Hackers Found a Way Into Humanoid Robots | Threat Wire
1 Quelle
Bits und so #1021 (Passwort für Laufwerk)
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten MergeForge: Resolve Git Conflicts in VS Code or Cursor Like in JetBrains

Thematisch verwandte Begriffe: MergeForge, Resolve, Conflicts, Code · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...