v8 and v9 fail for the second target OS about add-and-commit HOT 4 CLOSED

Yes, that worked!
Thank you very much for the quick response and advice.

from add-and-commit.

Since v8, the action doesn't run git pull by default. You can change to the previous behavior by using setting pull: --rebase in your inputs

from add-and-commit.

Thank you, @EndBug. I did as you advised, but got an error on the first target (ubuntu-latest):

Error: Error: error: cannot pull with rebase: Your index contains uncommitted changes.

I guess, this is because the produced binaries are part of the version control. The rest was committed and pushed to trigger the CI (build). But again, everything worked in v7.

Should I use add: 'app/${{runner.os}}/* --force --rebase' instead of pull: --rebase?

from add-and-commit.

Well, you can't use --rebase on git add, so that's a no for sure...
I think this relates to issue #492: it's a bit tricky to find a solution that works for every scenario, and the current is for sure not the best one...

It's a bit of a workaround, but why don't you try manually pulling before the action?

- run: git pull
- uses: EndBug/add-and-commit@v9
  with:
    add: # ...

To be honest, concurrency it's something this project was never great to handle: it's for sure something to improve in the future

from add-and-commit.