Pull request comments

On a pull request, Infragr.am posts a comment linking to the diagrams:

Infragr.am architecture diagram production

View the diagram →

Network, Compute, Data and Security views of what this pull request changes. Updated on every push; the link stays the same.

One comment per environment

Each environment gets exactly one comment. A new push edits that comment instead of adding another, so a pull request with ten pushes and two environments has two comments, not twenty. The environment name appears in the heading. An unnamed build has none.

The comment is posted by the Infragr.am GitHub App.

Comment modes

Set per repository in the dashboard: Repositories, then the settings icon (⚙) on the repository, then Pull request comments.

Mode	Behaviour
on-change (default)	Comments when the plan changes. A push whose plan is identical to one already diagrammed reuses that diagram and posts nothing new.
always	Comments, or updates the comment, on every accepted build, including reused ones.
off	Never comments. Diagrams are still built and appear in the dashboard.

When there is no comment

• The build was skipped at preflight. The step ends green with a notice. See Troubleshooting.
• The workflow isn’t triggered by pull_request, for example push or workflow_run. The diagram is in the dashboard, but there is no pull request to comment on.
• The comment mode is off, or it is on-change and the plan didn’t change.

Choosing lenses

The same settings dialog has Architecture lenses: Network, Compute, Data and Security. Each enabled lens is drawn as its own diagram, and at least one must stay on. Turning off lenses your team doesn’t read keeps the review focused. It doesn’t change how builds are counted.