Skip to content

Changing language to change implications of Automate#133

Merged
John Gluck (JohnGluck) merged 1 commit into
mainfrom
128-mapping---reference-to-automate-for-complex-flows
May 20, 2026
Merged

Changing language to change implications of Automate#133
John Gluck (JohnGluck) merged 1 commit into
mainfrom
128-mapping---reference-to-automate-for-complex-flows

Conversation

@JohnGluck
Copy link
Copy Markdown
Collaborator

Addressing comments in open issue

@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 20, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
qawolf 🟢 Ready View Preview May 20, 2026, 8:34 PM

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates wording in the “Getting good results with Mapping” documentation to clarify when users should switch from Mapping to Automate, addressing feedback from an open issue.

Changes:

  • Rephrased the “Use Automate…” guidance to emphasize converting flows into tests one-by-one with targeted prompts.
  • Simplified the section copy to reduce prescriptive examples about when Automate is required.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread qawolf/getting-the-most-out-of-mapping.mdx
@JohnGluck John Gluck (JohnGluck) merged commit 2372d4c into main May 20, 2026
3 checks passed
@JohnGluck John Gluck (JohnGluck) deleted the 128-mapping---reference-to-automate-for-complex-flows branch May 20, 2026 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Mapping - reference to "Automate" for complex flows

3 participants