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: "fixup: todos". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: todos 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: "fixup: safe cast". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: safe cast 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: "fixup: log forbidden pkt". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: log forbidden pkt 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: "fixup: simplify filter_map, tun". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: simplify filter_map, tun 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: "fixup: c-str literal". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: c-str literal 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: "fixup: inspect_err". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: inspect_err The message 10 is invalid: * The subject must start with a verb in imperative mood, but it started with: "One". Whether the word is in imperative mood is determined by whitelisting. The general whitelist is available at https://github.com/mristin/opinionated-commit-message/blob/master/src/mostFrequentEnglishVerbs.ts. You can whitelist additional verbs using "additional-verbs" input to your GitHub action (currently one or more additional verbs were thus specified). Moreover, you can also whitelist additional verbs in a file given as "path-to-additional-verbs" input to your GitHub action (currently no whitelist file was specified). Please check the whitelist and either change the first word of the subject or whitelist the verb. The original message was: One RouteManagerCommand per OS The message 11 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: "fixup: adjust early eslogger timeout". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: adjust early eslogger timeout The message 15 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: "fixup: Error::other". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: Error::other The message 16 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: "fixup: mention drop". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: mention drop The message 17 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: "fixup: broadcast capacity = 1". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: fixup: broadcast capacity = 1 The message 18 is invalid: * Expected the subject to start with a verb in imperative mood consisting of letter