Skip to content

Merge Statuspage incident and component guides into one guide #2447

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

PeyGis
Copy link
Contributor

@PeyGis PeyGis commented Jun 19, 2025

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Added docs pages

Please also include the path for the added docs

  • Quickstart (/)
  • Blueprint (/platform-overview/port-components/blueprint)
  • ...

Updated docs pages

Please also include the path for the updated docs

  • Quickstart (/)
  • Blueprint (/platform-overview/port-components/blueprint)
  • ...

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2447.d2ngvl90zqbob8.amplifyapp.com

@@ -1207,16 +1207,16 @@ export const availableGuides = [
logos: ["GitLab"],
link: "/guides/all/visualize-and-manage-gitlab-deployments",
},
// {
Copy link
Contributor

Choose a reason for hiding this comment

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

any reason not to delete this commented out text?

Also, i'm a bit confused since we have 2 very similar guides:

  • Create and Manage Statuspage Incidents
  • Visualize and manage your Statuspage incidents and components

is this intentional or can we remove one of them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, you're right. I'll delete the commented text, and delete the other similar guide. The Create and Manage Statuspage Incidents uses GitHub workflow for the action backend, whereas the visualize and manage uses our synced webhook, which is much simpler to configure.

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.

2 participants