Awesome Reviewers expert instructions

domains / / awslabs/aidlc-workflows

CI/CD Workflow Predictability

When configuring GitHub Actions for CI/CD, keep workflow outputs and triggers predictable: 1) Use safe, stable identifiers for artifacts/reports. Don’t build artifact names from values that can be invalid (e.g., raw branch/ref names). Prefer constants or explicitly sanitized values.

raw .md CI/CD Yaml

When configuring GitHub Actions for CI/CD, keep workflow outputs and triggers predictable:

1) Use safe, stable identifiers for artifacts/reports. Don’t build artifact names from values that can be invalid (e.g., raw branch/ref names). Prefer constants or explicitly sanitized values.

Example (stable artifact name):

# Prefer a constant over potentially invalid dynamic ref names
name: "report-head"
# In expressions:
# format('report-head')

2) Don’t redundantly declare default PR trigger types. For on: pull_request, opened, reopened, and synchronize are defaults—specify only the additional types you actually need (e.g., labeled).

Example:

on:
  pull_request:
    branches: [main]
    types:
      - labeled  # add only non-default events