The latest articles on DEV Community by Emre Armagan (@emre_armagan_a52113c8e7b0). https://dev.to/emre_armagan_a52113c8e7b0 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4059404%2Fea4c36f3-9002-482e-b33b-eec49059b8db.png https://dev.to/emre_armagan_a52113c8e7b0 en Emre Armagan Tue, 13 Oct 2026 03:40:50 +0000 https://dev.to/emre_armagan_a52113c8e7b0/atlasnvim-pr-reviews-and-issues-inside-neovim-5506 https://dev.to/emre_armagan_a52113c8e7b0/atlasnvim-pr-reviews-and-issues-inside-neovim-5506 <p>Hey everyone!</p> <p>I have been working on <code>atlas.nvim</code>, a plugin for managing GitHub, GitLab and Bitbucket PRs, plus Jira/GitHub/GitLab issues directly inside Neovim.</p> <p>My main goal is a unified workflow across all of them in a single interface, since I regularly use several!</p> <p>Some things it supports:</p> <ul> <li>PR reviews with inline comments, code suggestions and local notes</li> <li>LSP support inside the diff</li> <li>Issue and PR creation</li> <li>Repository browsing</li> <li>Pipelines and job logs</li> <li>Provider notifications and custom actions</li> </ul> <p>If you try it out, I would love to hear what works and what does not :)</p> <p><a href="https://github.com/emrearmagan/atlas.nvim" rel="noopener noreferrer">https://github.com/emrearmagan/atlas.nvim</a></p> neovim