gh-velocity risk#

Structural risk signals

Synopsis#

Where are structural risks in your codebase?

Risk signals identify single points of failure and knowledge concentration:

bus-factor Who knows what? Identifies files and directories where knowledge is concentrated in one or two contributors

Options#

  -h, --help   help for risk

Options inherited from parent commands#

      --config string   Path to config file (default: .gh-velocity.yml)
      --debug           Print diagnostic info to stderr
  -f, --format string   Output format: json, pretty, markdown (default "pretty")
      --new-post        Force a new post (skip idempotent update; implies --post)
      --post            Post output to GitHub (dry-run by default; set GH_VELOCITY_POST_LIVE=true for live)
  -R, --repo string     Repository in owner/name format
      --scope string    Additional GitHub search qualifier(s) ANDed with config scope

SEE ALSO#

• gh-velocity - GitHub velocity and quality metrics
• gh-velocity risk bus-factor - Knowledge risk per directory from git history