The message 1 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "refactor(tensors): Split interface Tensor into multiple interfaces". Please re-write the subject so that it starts with a verb in imperative mood. * The body does not contain any 'Signed-off-by: ' line. Did you sign off the commit with `git commit --signoff`? The original message was: refactor(tensors): Split interface Tensor into multiple interfaces Functions for element-wise and matrix operations are moved to two new interfaces. The generic formal type parameter has been changed to allow signed integer types in addition to floating-point types. The message 2 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "chore(tests): Split and fix generic tests after refactoring of tensors". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: chore(tests): Split and fix generic tests after refactoring of tensors The message 3 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "feat(simd): Add more SSE2, SSE4, and AVX2 intrinsics for integers". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: feat(simd): Add more SSE2, SSE4, and AVX2 intrinsics for integers The message 4 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "chore(orka.gl): Fix some compiler warnings". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: chore(orka.gl): Fix some compiler warnings The message 5 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "refactor(tensors): Simplify implementation of function for inner product". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: refactor(tensors): Simplify implementation of function for inner product The message 6 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "feat(simd): Add functions and some intrinsics for integers and longs". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: feat(simd): Add functions and some intrinsics for integers and longs The message 7 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "feat(tensors): Add tensor packages using SIMD for integers and longs". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: feat(tensors): Add tensor packages using SIMD for integers and longs The message 8 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "chore(simd): Port obsolescent syntax for arrays to Ada 2022 array syntax". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: chore(simd): Port obsolescent syntax for arrays to Ada 2022 array syntax The message 9 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "refactor(simd): Use static functions and new types for masks". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: refactor(simd): Use static functions and new types for masks

The following actions uses node12 which is deprecated and will be forced to run on node16: mristin/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/