`bacon test` with something like `insta` can endlessly trigger re-runs about bacon HOT 5 OPEN

I wasn't asking you to close the issue, you can keep it open until everybody thinks it's OK.
For once, git shouldn't be a requirement to use bacon.

from bacon.

If your project sources are controlled with git, you shouldn't have any problem:
I don't know insta but the file it creates, being automatically generated from sources, should probably be ignored, and changes on gitignored files don't trigger bacon runs.

Are you using another source version control system than git ?

from bacon.

No, but the snapshots should not be ignored. The snapshot files are the source of truth for snapshot tests. You can essentially think of their contents as the expected value in an assert_eq!()

from bacon.

I guess I could setup git to ignore the pending snapshots, but I kind of rely on pending snapshots to show up in git status to notice that I forgot to review

I can't recall a project that uses insta and ignores pending snapshots, but I also don't make a habit of checking .gitignore files. It could be a workable solution I suppose

Edit: I'll go ahead and give it a try :)

I'll re-open if I end up running into any issues with the different workflow

from bacon.

I occasionally get this as well, even though my pending snapshot files are under .gitignore for some reason.

from bacon.