News for hackers. Stuff that matters.
Re: by whirlwin on Thursday November 12, 2026 @04:18PM (#50474430)
Would like to hear from everyone: How are you dealing with PRs in 2026? It's our biggest bottle neck.

We are considering looking into attestations, e.g. through the SLSA spec: https://slsa.dev/ to ensure build provenance and verification before it is deployed.

Re: by miguelrios on Thursday November 12, 2026 @05:03PM (#50474965)
Would love to hear that too... it's getting incredibly expensive. One of our templates is a code review agent. https://agentrun.ai/blog/saving-80-percent-on-code-reviews-u.... But we're looking to do more beyond making the review cheap.
Re: by philipp-gayret on Thursday November 12, 2026 @10:35PM (#50477901)
For my own projects: Agents have access to managed tools which enforce quality metrics, build, test, and deploy all more or less in parallel and get it ready to go into git. Examples of metrics are: test coverage, allowed dependencies, linters and the usual. These tools run on the same machine where the software will be deployed (for performance reasons). These tools submit attestations for everything they do. I made my own system for it, it keeps track of everything. The whole process including docker build and deploy to a test env is 10s or less. (I find 10s is reasonable to achieve for all projects I've worked on). Secondly I run a daily process for all projects that runs another set of quality metrics ; picture for example dependencies out of date, tests getting too slow and similar topics. These become work for the agents to pick up. Review is me checking if the app does what it should at best. If it passes all the quality metrics, I don't care much for the code.

For clients (who are not that AI-pilled): They're liking CodeRabbit and developers are not reviewing as strictly anymore. Quality metrics are obtained via CI/CD and attached to PR's. If it's all green then most developers would give it a LGTM

Re: by jcarver on Thursday November 12, 2026 @10:43PM (#50477957)
You have two options:

1. Agentic merge queue. Lower risk PRs enter a queue and are auto-merged by a specialized agent. Higher risk PRs are still reviewed by humans. We're currently doing this for Dependabot PRs via a product we built: https://patchwave.ai/ , but the approach generalizes to any kind of PR.

2. Stop doing PRs. Review moves upstream into a multiplayer agent thread that's visible to the team - tag a teammate to pop in and look when you need feedback. PR checks move upstream into this thread as well, the agent just runs them as part of verifying its work. Push to main, ci checks run and deploy as normal from there.

We're at 1 now, but actively working towards moving to 2 and want to help other teams do the same.

Re: by biggestriverman on Friday November 13, 2026 @03:20AM (#50480079)
What I do is while tasks are being assigned to agents I work the the manager agent to ensure the tasks are correct and actually correspond to the goal of the project. The manager agent reaches out with blocking questions it cannot figure out itself. Then for review pre-release the code is verified against the assigned task, checked for bugs and security risks. Once all found issues are fixed it goes out.
Re: by DeepOntology on Friday November 13, 2026 @02:37PM (#50488624)
My own personal recipe:

1. No pull requests 2. I have separate strategy, code-writing, and commit agents 3. A reader that never saw the builder's reasoning checks each fix first 4. Full test run must be green on the exact commit 5. Verification / feature walk on staging

On the app I'm building (and its platform dependencies) I've made it through ~1200 commits and ~300k LOC without more than an occasional trivial regression/having to roll back... so, I think my strategy is working.