What this integration covers
- Placeholder summary line describing what the GitHub integration surfaces inside ScaleOps.
- Placeholder line covering which events are forwarded and how often.
- Placeholder line covering the permissions the integration asks for.
- Placeholder line covering how to scope the integration to particular clusters.
- Placeholder line covering what to check first when something does not arrive.
Before you start
Placeholder introduction paragraph. Real copy for the GitHub integration has not been written yet — this page exists to show the article layout, including how a linked reference sits inside body text.
- Placeholder prerequisite describing the access level needed in GitHub.
- Placeholder prerequisite describing the ScaleOps role needed to complete the connection.
Placeholder paragraph describing the shape of the connection and where the credentials are stored. This block is here to give the measure and leading something realistic to sit against.
Connecting GitHub
Placeholder paragraph introducing the configuration below.
apiVersion: v1
kind: ConfigMap
metadata:
name: scaleops-integration-placeholder
namespace: scaleops-system
data:
# Placeholder configuration — not a real payload.
provider: "placeholder"
enabled: "true"Placeholder paragraph explaining what to expect once the configuration is applied, and how long the first sync usually takes.
A note on scope
Placeholder callout paragraph. The comp puts a second, shorter highlight box at roughly this point in the article, so this one is here to hold that position.
Troubleshooting
Placeholder paragraph covering the first thing to check when events stop arriving, written at roughly the length the comp’s closing section runs to so the page ends on a realistic measure.
Placeholder closing paragraph.