Navo
Public demo — read-only replica of Navo service detail. Edit, add, and delete controls are disabled on this website.

PR merged

gitopspr-mergeSource control

Human-reviewed change lands on the default branch.

gitprdemo

Technical Summary

Application, IaC, or systems-deployment PR merges through normal review. That commit triggers the map-refresh job — not a manual diagram edit.

Advantages

  • Topology updates start from real code changes
  • Review stays on the PR path humans already use

Who / What / When / Where / Why

Who
Feature and platform teams
What
Merged pull request on main
When
On every accepted merge
Where
Git hosting (Azure DevOps, GitHub, etc.)
Why
Maps should refresh from verified source, not tribal knowledge

Related Services

Related Repos

  • pr-merge-service
  • pipeline-platform

Links

  • PR merged runbook

    wiki/wiki/pr-merge.md

    In-app wiki path (demo stub)

  • Source repository

    repohttps://example.com/repos/pr-merge

    Example repo link for the public demo

  • Ops dashboard

    urlhttps://example.com/dashboards/pr-merge

Add Service Link

Dev

In the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.

Local annotations (overlay)

In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.

Ready to contribute in a real deployment? Architecture maps ship through Git PRs — not browser-only edits. Share & export docs