Skip to content

docs(source-stripe): fix migration guide formatting, grammar, and duplicate content#76277

Draft
devin-ai-integration[bot] wants to merge 2 commits into
masterfrom
devin/1776109369-stripe-docs-improvements
Draft

docs(source-stripe): fix migration guide formatting, grammar, and duplicate content#76277
devin-ai-integration[bot] wants to merge 2 commits into
masterfrom
devin/1776109369-stripe-docs-improvements

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot commented Apr 13, 2026

Documentation Confidence Assessment

Overall Confidence: 3/5 capped: breaking changes require human review; zero-score dimension (connector sensitivity)

Dimension Score Rationale
Code Comprehension 5/5 Manifest-only YAML connector; all streams, auth, and pagination are fully declarative with no custom code.
API Documentation Quality 5/5 Stripe has comprehensive official API docs with auth guides, rate limits, changelogs, and OpenAPI specs (8 external doc URLs in metadata).
Change Scope and Risk 5/5 Under 10 net lines changed; grammar fixes, formatting corrections, and duplicate paragraph removal only.
Existing Doc Maturity 5/5 stripe.md is 511 lines with comprehensive coverage; stripe-migrations.md is 161 lines with good structure across 5 version sections.
Connector Sensitivity 0/5 Stripe is a top-tier certified connector (ql=400, sl=300) with active breaking change (6.0.0) documentation in scope.
Triggering Context 5/5 Triggered from a merged commit on master (breaking change 6.0.0 via PR 76095).

What I Verified vs. What I Inferred

  • Verified from code: The connector is manifest-only YAML. The 6.0.0 change replaces DpathFlattenFields with RecordExpander for invoice_line_items and subscription_items incremental streams. The breakingChanges metadata entry correctly scopes impact to these two streams with an upgrade deadline of 2026-05-12.
  • Verified from API docs: Stripe Events API retains events for 30 days (confirmed via official API reference). Invoice line items are nested at data.object.lines.data and subscription items at data.object.items.data, matching the connector's RecordExpander paths.
  • Verified from diff: The changelog date for 6.0.0 (2026-04-13) matches the merge commit timestamp. The PR link text [76095] matches the actual URL.
  • Inferred: Nothing was inferred; all changes are formatting/grammar corrections verified against the rendered Markdown and Docusaurus admonition syntax.

Areas of Concern

None identified. All changes are formatting corrections, grammar fixes, and removal of a duplicate paragraph. No substantive content was added or removed.


What

Fixes formatting, grammar, and structural issues in the Stripe source connector migration guide (stripe-migrations.md) following the v6.0.0 breaking change merged in #76095.

How

Corrections:

  • Fixed heading hierarchy: changed ### Upgrading to 5.6.0 to ## Upgrading to 5.6.0 for consistency with other version sections
  • Removed duplicate paragraph in the 5.0.0 section (was repeated verbatim twice)
  • Fixed "effected" to "affected" (two occurrences in 5.0.0 section)

Formatting fixes:

  • Converted three fenced ```note``` code blocks to proper :::note Docusaurus admonitions in the 5.6.0 section (these were rendering as raw code blocks instead of styled callouts)
  • Removed trailing whitespace and extra blank lines
  • Removed trailing colon from heading

Grammar fixes:

  • "previously sync data" to "previously synced data"
  • "pause all connection" to "pause all connections"
  • Minor rewording for clarity in the 5.0.0 and 5.6.0 sections

Review guide

  1. docs/integrations/sources/stripe-migrations.md — All changes are in this file. Focus on the 5.0.0 section (duplicate removal) and 5.6.0 section (admonition syntax fix).

User Impact

Improved readability and rendering of the Stripe migration guide. The :::note admonitions now render correctly in Docusaurus instead of appearing as raw code blocks. No functional changes to sync behavior or connector configuration.

Can this PR be safely reverted and rolled back?

  • YES

Note: I am an AI assistant (Devin) and have proposed these documentation updates based on a review of the connector source code and third-party API documentation. Reviewers may merge, modify, or close this PR as they see fit.

Link to Devin session: https://app.devin.ai/sessions/eab651a739434028ac0109cdb92fdd1c

devin-ai-integration Bot and others added 2 commits April 13, 2026 19:43
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Copy Markdown
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • 🛠️ Quick Fixes
    • /format-fix - Fixes most formatting issues.
    • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
      • Bump types: patch (default), minor, major, major_rc, rc, promote.
      • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
      • The promote type strips the RC suffix to finalize a release.
      • Example: /bump-version type=rc or /bump-version type=minor
    • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
  • ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
    • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
    • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
    • /ai-review - AI-powered PR review for connector safety and quality gates.
  • 🚀 Connector Releases:
    • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • ☕️ JVM connectors:
    • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
      Example: /update-connector-cdk-version connector=destination-bigquery
  • 🐍 Python connectors:
    • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
    • /poe source example lock - Alias for /poe connector source-example lock.
    • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
    • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
  • ⚙️ Admin commands:
    • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
      Example: /force-merge reason="CI is flaky, tests pass locally"
📚 Show Repo Guidance

Helpful Resources

📝 Edit this welcome message.

@devin-ai-integration devin-ai-integration Bot added area/documentation Improvements or additions to documentation team/documentation labels Apr 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-qbrjgr0wc-airbyte-growth.vercel.app

Built with commit d0d2766.
This pull request is being automatically deployed with vercel-action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants