velocirepo digest

Render a sparkline per source and project over the last 8 weeks, with the week’s findings, and post it as a comment on the long-lived “Weekly digest” issue labelled velocirepo-digest, for the problems no check was written for. It never opens or closes the tracking issue. Uses the workflow token, from --repo-token or VELOCIREPO_REPO_TOKEN. With --dry-run, the digest is printed instead.

velocirepo digest [OPTIONS]

Full --help output

Render a sparkline per source and project over the last 8 weeks, with the week's findings, and post it as a comment on the long-lived "Weekly digest" issue labelled velocirepo-digest, for the problems no check was written for. It never opens or closes the tracking issue.

Uses the workflow token, from --repo-token or VELOCIREPO_REPO_TOKEN. With --dry-run, the digest is printed instead.

Usage:
  velocirepo digest [flags]

Flags:
      --dry-run             print the digest instead of posting it
  -h, --help                help for digest
      --repo string         the data repository, owner/name (default: $GITHUB_REPOSITORY)
      --repo-token string   a token for the data repository (default: $VELOCIREPO_REPO_TOKEN)

Global Flags:
      --config string   config file (default: walk up for velocirepo.toml)
  -q, --quiet           suppress progress output
  -v, --verbose         enable debug logging

Options

--dry-run

print the digest instead of posting it

-h, --help

help for digest

--repo: string = $GITHUB_REPOSITORY

the data repository, owner/name

--repo-token: string = $VELOCIREPO_REPO_TOKEN

a token for the data repository

--config: string = walk up for velocirepo.toml

config file

-q, --quiet

suppress progress output

-v, --verbose

enable debug logging