Issue

Work with sfops issues

• sfp issue analyze

• sfp issue comment process

sfp issue analyze

USAGE
  $ sfp issue analyze -r <value> -i <value> [--json] [-e <value>] [-t <value>] [--sfp-server-url <value>] [-s]
    [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -i, --issue=<value>              (required) Issue number to be analyzed
  -r, --repository=<value>         (required) Repository in the format owner/repo (GitHub) or org/project/repo (Azure
                                   DevOps)
  -s, --setoutput                  Set the parsed issue inputs as output variables
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
      --loglevel=<option>          [default: info] logging level for this command invocation
                                   <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

ALIASES
  $ sfp gh issue analyze

See code: src/commands/issue/analyze.ts

sfp issue comment process

Process commands from GitHub issue/PR comments

USAGE
  $ sfp issue comment process -r <value> -i <value> -c <value> -b <value> -a <value> [--json] [-e <value>] [-t <value>]
    [--sfp-server-url <value>] [-g <value>...] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -a, --comment-author=<value>      (required) Comment author username
  -b, --comment-body=<value>        (required) Comment body text containing the command
  -c, --comment-id=<value>          (required) Comment ID
  -e, --email=<value>               Email address for authenticated user. Ignored if --application-token is provided.
                                    Can be set via SFP_SERVER_USER env var.
  -g, --logsgroupsymbol=<value>...  Symbol used by CICD platform to group/collapse logs in the console. Provide an
                                    opening group, and an optional closing group symbol.
  -i, --issue-number=<value>        (required) Issue or PR number
  -r, --repository=<value>          (required) Repository identifier in format owner/repo (GitHub/GitLab) or
                                    org/project/repo (Azure DevOps)
  -t, --application-token=<value>   Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                    (CLI flags take precedence over env vars).
      --loglevel=<option>           [default: info] logging level for this command invocation
                                    <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --sfp-server-url=<value>      URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                    config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Process commands from GitHub issue/PR comments

EXAMPLES
  $ sfp issue comment process --repository owner/repo --issue-number 123 --comment-id 456 --comment-body "sfops extend --hours 24" --comment-author user123

  $ sfp issue comment process --repository flxbl-io/sfp-pro --issue-number 42 --comment-id 789 --comment-body "renew environment" --comment-author developer

See code: src/commands/issue/comment/process.ts