Change the default task to watch then we can just execute: funzzy to start watching.

provide options to ignore files and .gitignore

It would be useful if we could have some sort of visual/sound notification after a task is completed. It's interesting for a long task where we usually lose focus on what is being done.

The original behaviour was that funzzy continues running after any of the tasks fails and wait for the next change.

Expected

• Funzzy process continues running after any task is failed or errored

Current

• Funzzy process dies if any task exits with 1

Basically run fzz init once if it detects that .watch.yaml is missing on the current folder, but first ask for the user if they want to proceed and create a .watch.yaml

Make more sense if run: be at same level of when:
example:

- name: run my tests
  run: make test
  when:
    change: ['lib/**', 'spec/**']
    ignore: 'tmp/**'

Using some app that parse Markdown to html documentation like:

• http://www.mkdocs.org/
• https://github.com/vmg/redcarpet
• https://github.com/johannhof/markdown.rs

It seems that the command is freezing sometimes

Using this mode you can run the configured commands in an interval of time.

Add the verbose option for debug purposes. It should print all paths found during the Watches.watch.

Provide a way to funzzy works with stdout then will be possible to run like entr runs:

ls -d * | funzzy sh -c 'make && make test'

It could create the yaml file also.

Today when yaml has bad format we get this error:

thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: ScanError { mark: Marker { index: 222, line: 10, col: 4 }, info: "while parsing a flow sequence, expectd \',\' or \']\'" }', ../src/libcore/result.rs:688

We need a better error message.

Validates config file presence if it has no stdin or arbitrary command.

The idea is to be able to quickly validate your rules via some sort of dry-run feature. Very useful when trying to create a rule that is a bit more specific

Acceptance Criteria

• The user is able to quickly verify if a file change will trigger their rule
• The defined command for that rule should not be executed

Today we have a bunch of warning that shows on the compilation. Would be nice to fix them.

warning: unused import: `std::process::*;`
 --> src/cmd.rs:3:5
  |
3 | use std::process::*;
  |     ^^^^^^^^^^^^^^^^
  |
  = note: #[warn(unused_imports)] on by default

warning: unused extern crate
 --> src/lib.rs:4:1
  |
4 | extern crate rustc_serialize;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: #[warn(unused_extern_crates)] on by default

warning: unused extern crate
 --> src/lib.rs:5:1
  |
5 | extern crate docopt;
  | ^^^^^^^^^^^^^^^^^^^^

warning: unused extern crate
 --> src/cli/watch.rs:2:1
  |
2 | extern crate glob;
  | ^^^^^^^^^^^^^^^^^^

warning: unused extern crate
 --> src/yaml.rs:2:1
  |
2 | extern crate glob;
  | ^^^^^^^^^^^^^^^^^^

warning: unused import: `std::process::*;`
 --> src/cmd.rs:3:5
  |
3 | use std::process::*;
  |     ^^^^^^^^^^^^^^^^
  |
  = note: #[warn(unused_imports)] on by default

warning: unused extern crate
 --> src/cli/watch.rs:2:1
  |
2 | extern crate glob;
  | ^^^^^^^^^^^^^^^^^^
  |
  = note: #[warn(unused_extern_crates)] on by default

warning: unused extern crate
 --> src/yaml.rs:2:1
  |
2 | extern crate glob;
  | ^^^^^^^^^^^^^^^^^^

    Finished dev [unoptimized + debuginfo] target(s) in 24.30 secs

Error: SHA256 mismatch
Expected: b34ee2d8339a54f7edaf122394a5074ad9c77b554629560322f5fc70c29a6b39
Actual: 6cfce5267b639fc9d2ef4cbbe299e6c304e0984f1e73f6977debdad6f92af343
Archive: /Library/Caches/Homebrew/funzzy-0.3.0.tar.gz

This procedure used to be via travis.ci but the service has changed and no longer is supported. So the idea is to move it to github actions.

We are going to need self-hosted https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
Here an example of how it's done https://github.com/skx/github-action-publish-binaries

The idea is to allow a long-running fzz process to have a log output for debugging purposes.

• By default, it shouldn't log,
• Log output if --output /var/log/foo.log is passed

Try this:

- name: run tests
  run: ["yarn test {{filepath}}", "echo '{{filepath}}' | sed -r 's\/.tsx/\/'" ]
  change: 'src/**'

And once the cli attempts to load the rules it panics:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ScanError { mark: Marker { index: 258, line: 8, col: 34 }, info: "while parsing a quoted scalar, found unknown escape character" }', src/rules.rs:92:57
stack backtrace:
   0: rust_begin_unwind
             at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/panicking.rs:67:14
   2: core::result::unwrap_failed
             at /rustc/5680fa18feaa87f3ff04063800aec256c3d4b4be/library/core/src/result.rs:1651:5
   3: fzz::rules::from_file
   4: fzz::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

- name: run my tests
  run: make test
  change: ['src/**', 'test/**']

I save the file on src/index.js and for some reason it runs the tests 5 times...

Hi, I'm not sure if this is out of scope.
Is working fine with vim or the default visual editor on the os but not working with editor like vscode, pulsar editor or sublime text
also not working with nano
the output is just
Funzzy: Watching...
I'm using Linux mint as OS

Here the yml file:

- name: run my test
  run: [
    'ls -a',
    'echo helooooo'
  ]
  change: "**"

also i want to point out that inotifywait is working fine:

while inotifywait -e close_write **; \
do clear && \
    date +"%T"
    ls -la
done

Any idea? Thank you

For instance, I have the follow rules:

## Funzzy events file
# more details see: https://github.com/cristianoliveira/funzzy
#
# list here all the events and the commands that it should execute

- name: Run linter
  run: 'yarn lint'
  change: 'src/**'

- name: Trigger cypress
  run: 'touch ./cypress/integration/features/apm-validations.spec.js'
  change: 'src/**'

And if I remove one of them it goes back to have a feedback

Current behaviour

funzzy --target=lint                                                  
thread 'main' panicked at 'No rules found for the given filter', src/cli/watch.rs:141:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected

No rules were found for the given target

Available tasks:
 - checks
 - tests
 - build

Would be nice to have some "real" examples. For example for a js/ruby/python/rust project. So we should create an examples folder with a bunch of them

Just a required I had another day where I wanted to avoid changing my .watch.yml file just to add a new flag, while testing something. Maybe fzz could receive flags and pass down to the commands like:

fzz -t test -- --verbose
# --verbose is passed to the test task in this case `jest --verbose`

Currently when the .watch.yaml is invalid it shows a generic error, it must point the issue and instruct how to fix

Concat current folder with watched folder for matching.

- name: run tests
  when: 
    change: 'tests/**'
    run: make tests

That way avoiding that strange **/somenthin/** that is ugly.

run "funzzy init" and then run "funzzy watch" will get some error:

thread 'main' panicked at 'Unable to load configuration: ScanError { mark: Marker { index: 179, line: 8, col: 2 }, info: "while parsing a block mapping, did not find expected key" }', ../src/libcore\result.rs:799 rc/cli/init.rs

it seems the init command produce incorrect .watch.yaml file:
run:'ls -a' should be run: 'ls -a' .

See