Automation

The CLI runs unattended in one place: publishing documentation from CI with wseng cicd publish-docs. Every other command runs on an engineer's machine with their own GitHub login, Google account, and TrueFoundry token.

GitHub Action

jobs:
    publish-docs:
        runs-on: ubuntu-latest
        permissions:
            contents: read
            id-token: write
        steps:
            - uses: actions/checkout@v4
            - name: Publish Docs
              uses: trilogy-group/ws-eng-cli@main
              with:
                  command: wseng cicd publish-docs --overrides .doc.overrides.env

The Action assumes its aws-role input to upload doc assets to S3 and reads the Scalar token from shared-github-action-secrets.

A line that names a retired command prints a warning and does nothing, so an old workflow stays green until you remove the step. The shared ws-lambda-process ticket-check, auto-release, auto-merge, and close-inactive workflows still run through the Action until their retirement ships (ws-eng-cli#1304).

What Runs Automatically

Board moves trigger no CLI command. When a ticket moves to Review, Done, or Accepted, the Nex platform marks its linked PRs ready for review, requests the reviewer, and on Done or Accepted approves the PRs in repositories without a .nex.json gates block.

Issue created: triggers no CLI command. The Nex platform adds the issue to the project board, sets Project, and defaults Priority to Standard and the issue type to Feature.

Related Docs

Ticket Lifecycle Workflow

Commands commonly used day to day.

GitHub Action Reference

Complete action.yml specification.