Add gh-aw.staged and deployment.environment to OTLP conclusion spans

[Copilot]

awInfo.staged was read nowhere in sendJobConclusionSpan, making it impossible for OTLP backends to distinguish dry-run executions from production runs — polluting failure metrics and firing alerts on staged noise.

Changes

• send_otlp_span.cjs — sendJobConclusionSpan:

  • Reads awInfo.staged === true into a staged boolean
  • Pushes gh-aw.staged (bool) to span attributes
  • Pushes deployment.environment ("staging" | "production") to resourceAttributes, following OTel semantic conventions

• send_otlp_span.test.cjs — new describe("staged / deployment.environment") covering:

  • staged absent → gh-aw.staged=false, deployment.environment="production"
  • awInfo.staged=true → gh-aw.staged=true, deployment.environment="staging"
  • awInfo.staged=false → gh-aw.staged=false, deployment.environment="production"

// After reading other awInfo fields:
const staged = awInfo.staged === true;

// Span attribute
attributes.push(buildAttr("gh-aw.staged", staged));

// Resource attribute (OTel semantic convention)
resourceAttributes.push(buildAttr("deployment.environment", staged ? "staging" : "production"));

[Copilot]

Pull request overview

Adds explicit “staged vs production” signals to OTLP job conclusion spans so observability backends can separate dry-run noise from real runs.

Changes:

• Read awInfo.staged into a boolean and emit gh-aw.staged span attribute.
• Emit deployment.environment resource attribute as "staging"/"production" based on staged.
• Add unit tests covering default behavior and both awInfo.staged boolean cases.

Show a summary per file

File	Description
actions/setup/js/send_otlp_span.cjs	Adds gh-aw.staged span attribute and deployment.environment resource attribute in sendJobConclusionSpan.
actions/setup/js/send_otlp_span.test.cjs	Adds test coverage validating staged and environment attributes across staged unset/true/false.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0