Skip to content

docs: Update documentation of frame graphs #40

docs: Update documentation of frame graphs

docs: Update documentation of frame graphs #40

Triggered via push March 30, 2024 16:46
Status Failure
Total duration 10s
Artifacts
Check commit message style
2s
Check commit message style
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Check commit message style
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: "orka: Use generated ID instead of a name to identify resources". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: orka: Use generated ID instead of a name to identify resources 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: "orka: Raise an exception if resource is cannot be imported or exported". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: orka: Raise an exception if resource is cannot be imported or exported 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: "orka: Replace function Add_Graph with Connect to connect other graphs". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: orka: Replace function Add_Graph with Connect to connect other graphs 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: "orka: Add procedure Write_Graph to save Frame_Graph object". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: orka: Add procedure Write_Graph to save Frame_Graph object 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: "orka: Change function Connect with parameter To to be a procedure". 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: orka: Change function Connect with parameter To to be a procedure Since the function call providing a non-empty array of resources to the parameter To will return zero exported resources, it has no use to return a record containing two empty arrays. 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: "orka: Remove unneeded type External_Resources". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: orka: Remove unneeded type External_Resources 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: "docs: Update documentation of frame graphs". Please re-write the subject so that it starts with a verb in imperative mood. The original message was: docs: Update documentation of frame graphs
Check commit message style
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mristin/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Check commit message style
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/