Sprkl Docs
SupportSprkl websiteJoin Sprkl betaJoin Sprkl for CI
latest (0.0.70)
latest (0.0.70)
  • What is Sprkl?
  • Getting started
    • Install Sprkl
    • Instrument your code
      • Bare metal
      • Docker
      • Kubernetes
    • Start with a sample project with Docker Compose
  • Features
    • Instrumentation
      • Frontend tracing - NEW!
      • Selenium tracing - NEW!
      • Static analyzed code risks - NEW!
    • Dashboard
      • Personal vs. Global
      • Code Block Reference
    • Code markups
    • System Graph
    • Jaeger tracing
    • Jest integration
    • Detect runtime security vulnerabilities
  • Integrations and supported stack
  • Concepts
    • Analysis
  • FAQ
  • Support
  • Sprkl for GitHub Actions
    • Overview
    • Setup
    • Pulling Sprkl data to your IDE for further debugging
  • Troubleshooting
Powered by GitBook
On this page
  1. Sprkl for GitHub Actions

Overview

PreviousSprkl for GitHub ActionsNextSetup

Last updated 2 years ago

Sprkl for GitHub Actions is composed of two components:

These components work together to provide pull-request telemetry feedback.

Sprkl Reviewer relies on the Sprkl Action (GitHub Actions), which auto-instruments your Node.js code changes ( & ) and collects telemetry data, and traces about the workflow execution.

Get the Sprkl CI report

  1. Push your code change.

  2. Create a Pull Request with your recent changes.

  3. Wait for the actions to complete and get the Sprkl report inside the Conversation tab.

Sprkl Reviewer
Sprkl Action
OpenTelemetry
Sprkl
How it works