Mislav Marohnić

Thanks for reporting. I also wanted to switch Google to OAuth. If someone has the time to step up before me, send me a pull request

Amazing! Here's an issue for ya: justification on your article text! Scroll through your article again to see where it bites nastily

/cc @ztombol @jasonkarns for :eyes: since I know they are big users of Bats.

I've renamed this issue to not read like an official announcement anymore. This is open source. You're welcome to fork any project and continue maintaining it. You're welcome to let...

> Rather than making it more difficult for others to find this fork, how about letting these folks in and let them run the original project? 1. I didn't make...

> Nothing in that ticket sounded like an official announcement, by the way. Except for this part: **“⚠️ [ANNOUNCEMENT] REPO MOVE!”** > If you have the power to edit issues,...

That's weird; for me bash 4.3.42 works with bats just as well as bash 3.2. Can you try to reproduce the error with: ``` sh bash -c 'echo $BASH; let...

Can you isolate the smallest test file that fails with the error you described originally? Ideally, `bats mytest.bats` should fail. Then paste us that `*.bats` file. Thanks!

I wouldn't recommend doing so, since that flag would affect the operation of bats itself. I suggest you find a way to write tests that are not dependent on `pipefail`.

Woah, nasty. Didn't know that. How should we warn the people? We don't have tutorials on writing actual tests (this is supposed to be left as an exercise to the...