- 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...

Add the option to execute:

> make help
build                          Execute all the tests and build funzzy binary
help                           Lists the available commands. Add a comment with '##' to describe a command.
install                        Install funzzy on your machine
tests                          Execute all the tests

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' .

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

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.

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.

Run the rule's commands once before when flag with "run_on_init".

e.g.:

• name: run my test run: 'make tests' change: 'src/**' run_on_init: true

This would run the make tests once on start, even if nothing changed, and then start the watcher.

The flag is set to false by default, if the key is not present on the yaml or if values can't be assumed.

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

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/**'

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

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

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.

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

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