@amykit/plugin-command-gate

A gate that runs the target repository's own commands.

A plugin for amy. It provides the gate port.

Install

npm install -g @amykit/plugin-command-gate

Then name it in ~/.amy/config.yaml:

workflows:
  your-profile:
    plugins:
      - "@amykit/plugin-command-gate"

Configuration

plugins:
  "@amykit/plugin-command-gate":
    baseBranch: {}
    checkouts: {}
    commands: <record>
    defaultBranch: "main"
    timeoutMs: 1800000

| Setting | Type | Required | Default | What it is | | :-- | :-- | :-- | :-- | :-- | | baseBranch | record | no | {} | where one repository's base branch is, instead of the fallback. A repository named here has its work cut from, and its pull requests opened against, that branch | | checkouts | record | no | {} | where one repository's checkout is, instead of under the workspace root, which is where the gate's commands run | | commands | record | yes | | the check commands per repository, with a default fallback | | defaultBranch | string | no | main | the branch new work is cut from, which is not always main | | timeoutMs | number | no | 1800000 | how long one check may run before it is given up on |

Every field is checked at boot against the schema this package declares. A key that is not one of the above is a refusal naming the plugin and the key, not a setting that silently never applied.

Where the reasoning is

• Writing a plugin
• Reference: plugins
• Ports and the registry

Licence

MIT