Skip to content

Allow a working directory to be specified #191

@shadowhand

Description

@shadowhand

We are adding some additional (micro) services to our project, so now we have:

composer.json
composer.lock
services/
  foo/
    package.json
    package-lock.json

I'd like to be able to check for changes to services/foo/package{-lock,}.json and execute npm install but within the services/foo directory.

Is there any way that I can tell CaptainHook to execute the action in a different directory? I'm looking for something like:

{
  "action": "npm install",
  "options": {
    "in-directory": "services/foo"
  },
  "conditions": [ ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions