dkargatzis

6 ms·

1.
by dkargatzis 7mo ago
There is a preview environment that is currently free for both private and public repositories (at least for now). Early access also helps us expand the rule set and harden the core engine.
2.
by dkargatzis 7mo ago
Great stuff, I just had a look at the langchain-ai, nextjs, and tailwindcss rulesets. I'll try them out in our internal repos. As for your question, the evaluation loop has access to the PR diff and can identify the file paths affected
3.
by dkargatzis 7mo ago
Yes, both public and private. There is a guide with instructions in the repo.
4.
by dkargatzis 7mo ago
Hi HN! Maintainers are increasingly dealing with large volumes of low-context PRs, especially as AI coding tools make it easier to generate changes without the surrounding intent. Many repos already define contribution expectations in place
5.
Show HN: Turn .cursorrules / repo guidelines into GitHub pre-merge checks (OSS)(watchflow.dev)
4 points by dkargatzis 7mo ago|8 comments
6.
by dkargatzis 7mo ago
A PR kill switch is tempting, but it also kills collaboration. What we’re building instead looks at review-time signals rather than hard blocks. It surfaces why a PR is expensive to review: - diff surface vs scope - files touched vs CODEOWN
7.
The Warestack manifesto – Enforce DevOps best practices(warestack.com)
1 points by dkargatzis 2y ago|1 comments
8.
by dkargatzis 2y ago
Hi HN, “It’s deployment day, and last-minute surprises disrupt your team. Sound familiar? You’re not alone.” Today's development tools often operate in silos. Skipped reviews, deployment failures, and overlooked issues can still result