---
title: "Discussion on \"Anatomy of a breaking change: one pull request, three teams, two alerts\" | Hashnode"
description: "Discussion on \"Anatomy of a breaking change: one pull request, three teams, two alerts\". One example pull request from OpenAPI change to change history: which changes break, how the score adds up, and who gets told."
url: "https://hashnode.com/posts/anatomy-of-a-breaking-change-one-pull-request-three-teams-two-alerts/6af8b08d74c95981d4b545f4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Anatomy of a breaking change: one pull request, three teams, two alerts](https://graphwake.hashnode.dev/anatomy-of-a-breaking-change-one-pull-request-three-teams-two-alerts?utm_source=hashnode&utm_medium=feed)

One example pull request from OpenAPI change to change history: which changes break, how the score adds up, and who gets told.

1d ago · 11 min read · graphwake.hashnode.dev  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#openapi](https://hashnode.com/tag/openapi)
-   [#microservices](https://hashnode.com/tag/microservices)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Graphwake](https://hashnode.com/@graphwake)

@graphwake · Vancouver, Canada

  
[View profile](https://hashnode.com/@graphwake)

Founder of Graphwake. API changes between teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
