New circular dependency: OrderService ↔ ShippingService
HIGHShippingService.java:88 — orderService.markShipped(orderId)
GitHub integration
Catch architectural drift before it merges
On every pull request, Archynt analyzes the base and head commits, diffs the design issues between them, and posts the result straight to GitHub — so a new circular dependency or god-service shows up as a failing check, not a surprise three sprints later.
#482 — Ship inventory reservation from checkout
archynt/architecture · feature/inline-reservation → main
OrderController now depends on InventoryRepository directly
MEDIUMOrderController.java:54 — inventoryRepository.reserve(...)
How PR checks work
01
Triggered by GitHub
A pull_request webhook (opened, synchronize, reopened) starts the check automatically — no polling, no manual trigger from Archynt.
02
Diffs the graph, not the diff
Both the base and head commits are analyzed into full architecture graphs; the check compares the design issues each one produces, not the raw code diff.
03
Deterministic verdict
PASS if no new issues appear, FAIL if the PR introduces a HIGH-severity issue, WARN otherwise — same detectors used everywhere else in Archynt, not an LLM call.
04
Native GitHub check run
Results post as a check run (with a markdown summary of introduced and resolved findings) once the GitHub App is installed on the repository.
05
Works without the app, too
Without the GitHub App, a configured token still gets the result posted as a PR comment and commit status — just without the native check-run UI.
06
Private repos supported
The GitHub App installation token is also used to clone private repositories for analysis, so no separate credentials are needed.
Ready to see it on your system?
Run an analysis or jump straight into your organization workspace.