Task•3d ago

Task and tracking dir modtime

Hello. Let's say I'm changing tools/cmd/main.go and want to make a task that will track it by pattern. I know that this pattern will track any file in dir recursively.

  check:
    sources:
      - tools/**/*
    cmds:
      - echo 'changed'
    method: 'timestamp'

  check:
    sources:
      - tools/**/*
    cmds:
      - echo 'changed'
    method: 'timestamp'

But these patterns will not, even if dir modtime being updated when any internal content has been changed.

  check:
    sources:
      - tools/*
    cmds:
      - echo 'changed'
    method: 'timestamp'
  check:
    sources:
      - tools/cmd
    cmds:
      - echo 'changed'
    method: 'timestamp'

  check:
    sources:
      - tools/*
    cmds:
      - echo 'changed'
    method: 'timestamp'
  check:
    sources:
      - tools/cmd
    cmds:
      - echo 'changed'
    method: 'timestamp'

Is this intentional? For compatibility purposes with different file systems?

Solution:

Hi @sedyh, This happens because Task actually ignores directories and only cares about files....

Jump to solution

1 Reply

Solution

andreynering•3d ago

Hi @sedyh, This happens because Task actually ignores directories and only cares about files.

Gaming

Programming

Task and tracking dir modtime

Did you find this page helpful?