From 2abb34f0e7be40035d713f1d548eb8f3c4ac3b4c Mon Sep 17 00:00:00 2001 From: Tim te Beek Date: Thu, 17 Apr 2025 10:25:22 +0200 Subject: [PATCH] Link to automating breaking changes --- docs/user-documentation/workshops/recipe-authoring.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/user-documentation/workshops/recipe-authoring.md b/docs/user-documentation/workshops/recipe-authoring.md index 1971f0c9..d380e788 100644 --- a/docs/user-documentation/workshops/recipe-authoring.md +++ b/docs/user-documentation/workshops/recipe-authoring.md @@ -508,6 +508,10 @@ Because of that, there's a temptation to put the methods directly onto the class For a full understanding of traits, check out our [documentation on traits](https://docs.openrewrite.org/concepts-and-explanations/traits). +### Automating breaking changes + +Now that you've seen the various ways in which you can write recipes, you're perfectly positioned to start [automating breaking changes](https://docs.openrewrite.org/authoring-recipes/automate-breaking-changes). + ## Recipe conventions and best practices We've documented the most important [recipe conventions and best practices](https://docs.openrewrite.org/authoring-recipes/recipe-conventions-and-best-practices) to help you write recipes that are safe, idempotent, and efficient. Where possible, we've automated these checks in the unit testing framework, to help you catch issues early.