Bug 1698074, run flow-to-ts in automation to keep track of errors

[Pike]

No description provided.

[Pike]

I think this is a good-enough starting point. I haven't yet figured out how to get an error count, but right now this is at 767 TS errors.

[mathjazz]

Thanks!

Why do you need to git commit the changes before running the script? And why do you need to run git diff (to debug?)?

Also, a bug explaining the motivation or a comment in bug 1685565 would be welcome.

[mathjazz]

I guess the empty line is not empty?

[Pike]

Why do you need to git commit the changes before running the script? And why do you need to run git diff (to debug?)?

I want to add visibility into what the steps do, and what the code looks like that is creating errors. The commit and diff on the first step is just for the sake of completeness. I really care about exposing the changes that flow-to-ts does, but sadly git didn't cooperate with me at all so far. That's what that's commented out.

Maybe I'll use https://git-scm.com/docs/git-bundle, but I didn't want to spend too much time on this workflow for now, and rather iterate. I found it more interesting to get the flow up, so that we can use it in April's PR.

[mathjazz]

Thanks for clarifying!