Otto Kekäläinen

The options above sound good to me!

Relevant part (hopefully): > make[3]: Entering directory '//storage' > /bin/bash ../libtool --quiet --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 -fdebug-prefix-map=/=. -fstack-protector-strong -Wformat -Werror=format-security -funsigned-char...

Looks like the same bug affects MySQL 8.0 as well: https://github.com/jabberd2/jabberd2/issues/192

I seem to have bumped into the same bug. The line `git add .gitattributes && git commit -m "Add .gitattributes file"` fails with: ``` + git add .gitattributes fatal: not...

Yes, I am using a fork so I can debug.

Confirm: I saw this bug because the line `- uses: actions/checkout@master` was accidentally omitted. So user error. Maybe @Kubitomakita's problem in https://github.com/BracketSpace/Notification-Signature/blob/2111b3057efe3120f4a7e4dc249ec853e8e443d5/.github/workflows/stable.yml#L97-L113 is that he is using artifacts built from...

That is because of https://github.com/Seravo/gnitpick/blob/master/gnitpick.py#L174-L188 Should we change Gnitpick to check only the last 3 commits instead? Or just one?

You can inspect what happened by looking at the build log in https://travis-ci.org/github/Seravo/wordpress/jobs/660968721 ``` $ python3 ./gnitpick.py Travis-CI detected, reading git revisions from environment fatal: ambiguous argument '': unknown revision...

Changed to WIP status. Gnitpick needs to mature a bit more before this is ready for prime time.

With new wp-cli tools and our own `wp-fix-languages` we are one step closer to not having to use composer for language pack installations in the future anymore.