Skip to content

include vs includes? #18

@jimsheldon

Description

@jimsheldon

Hello!

We are very interested in using this plugin, but we are hoping to "future proof" it as much as possible.

Currently the required syntax is:

   when:
      changeset:
        includes: [ **/**.js, **/**.css, **/**.html ]

and

trigger:
  changeset:
    includes: [ **/**.go ]

All other drone syntax seems to use include rather than includes. Would you consider a new version of this plugin with a breaking change that switches to include to match drone's official syntax? Or maybe there is a way this plugin could support both include and includes?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions