Skip to content

readme: fix some diagrams #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 4, 2025
Merged

readme: fix some diagrams #51

merged 1 commit into from
Jun 4, 2025

Conversation

wasaga
Copy link
Collaborator

@wasaga wasaga commented Jun 4, 2025

No description provided.

@Copilot Copilot AI review requested due to automatic review settings June 4, 2025 17:26
Copy link

@Copilot 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

This PR updates the README diagrams and example configuration to fix and clarify the application flow.

  • Updated the sequence diagram to reposition "Your App Backend" for improved clarity.
  • Modified the GET request endpoint in the example route configuration to reflect the correct Pomerium routing path.
Comments suppressed due to low confidence (2)

README.md:168

  • [nitpick] The repositioning of 'Your App Backend' in the sequence diagram improves clarity; please confirm that the new order accurately reflects the intended flow of interactions.
participant C as Your App Backend

README.md:206

  • The updated GET request endpoint in the example configuration now points to the Pomerium routing path; please ensure that any related documentation is updated accordingly.
GET https://mcp-demo-app.yourdomain.com/.pomerium/mcp/routes HTTP/1.1

@wasaga wasaga merged commit eb49828 into main Jun 4, 2025
2 checks passed
@wasaga wasaga deleted the wasaga/readme-fixes branch June 4, 2025 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant