Cloudsmith CI investigation

This composite action wraps the Cloudsmith Package Insights Docker action and lets you either:

1. Provide log text directly, or
2. Provide the name of another job in the same workflow run whose logs will be fetched automatically via the GitHub API and passed to the underlying action.

Inputs

Name	Required	Description
api-key	Yes	Cloudsmith API key (exported to the underlying action as CLOUDSMITH_API_KEY).
log	No*	Raw build/install log text or a single line of URLs. Mutually exclusive with job-name.
job-name	No*	The name of another job (exact name: value) in the same workflow run. Mutually exclusive with log.
follow-up	No	Extra instructions to display in the output (e.g. Slack channel or contact).

*You must provide exactly one of log or job-name.

Behavior

• If log is supplied, it is forwarded directly.
• If job-name is supplied, the action:
  • Lists jobs for the current run_id.
  • Finds the job with the matching name.
  • Downloads the workflow run logs archive (gh api .../logs).
  • Extracts and concatenates log files for that job.
  • Writes the concatenated content to job.log.
  • Passes the file path (job.log) to the base action so it can read the file directly (avoids GitHub output truncation limits).

Usage Examples

A. Direct Log Input

jobs:
  insights_direct:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run insights with provided logs
        uses: cloudsmith-io/cloudsmith-ci-insights-action@main
        with:
          api-key: ${{ secrets.CLOUDSMITH_API_KEY }}
          log: |
            Fetching package...
            Received 403 for package cloudsmith/example/pkg

B. Using Job Name

jobs:
  build:
    name: Build Job
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: |
          echo "Pretend build that fails to fetch a package" >&2
          echo "403 GET https://dl.cloudsmith.io/..." >&2
      - run: sleep 2

  analyze:
    runs-on: ubuntu-latest
    needs: build
    steps:
      - uses: actions/checkout@v4
      - name: Analyze build job logs
        uses: cloudsmith-io/cloudsmith-ci-insights-action@main
        with:
          api-key: ${{ secrets.CLOUDSMITH_API_KEY }}
          job-name: Build Job

Notes / Limitations

• The wrapper uses the octokit SDK with the automatically provided GITHUB_TOKEN to retrieve logs.
• Very large logs are written to a file and the file path is passed (not the contents), avoiding step output truncation. Extremely huge logs may still risk disk space/time; consider filtering if multi-megabyte.
• Matching is exact on the name: you set for the job (case sensitive per API response). Ensure consistency.